Api Plugin Deprecation¶

Provide an additive deprecation path for independently upgraded plugin hosts.

Generated example

This page is generated from evaluations/scenarios/api-plugin-deprecation.yaml. The scenario YAML remains the executable source of truth.

Request¶

Repository evidence¶

No repository signals.

Expected resolution¶

Resolution layer	Expected
Profile	—
Modifiers	—
Language adapters	—
Framework adapters	—

Normalized context¶

{}

Skill modes¶

None.

Conflict decisions¶

None.

Significant decisions¶

None.

Principles under test¶

Forbidden outcomes¶

Remove the callback in a compatible release.
Export private host state as the replacement.

Scenario source¶

schema_version: 0.10.0
id: api-plugin-deprecation
description: Provide an additive deprecation path for independently upgraded plugin
  hosts.
input:
  skill: api-and-compatibility
  mode: public-library
  profile: plugin-or-extension
  modifier: public-api
  task: Replace a supported extension callback.
expected:
  active_principles:
  - backward-compatibility
  - semantic-versioning
  - principle-of-least-astonishment
  constrained_principles:
  - hyrums-law
  suppressed_principles: []
forbidden:
- Remove the callback in a compatible release.
- Export private host state as the replacement.
principles_under_test:
- backward-compatibility
- semantic-versioning
- principle-of-least-astonishment
- hyrums-law