agentera 3.0.0-dev.41 → 3.0.0-dev.47

package/bundle/references/cli/audience-namespace-cli-migration.yaml

@@ -1,395 +0,0 @@
-schema_version: agentera.audience_namespace_cli_migration.v1
-status: target_design_contract
-purpose: >-
-  Target CLI command tree, audience namespace grouping, and phased alias migration
-  policy for the Run 2 hybrid CLI consolidation. Documents the post-migration surface
-  before parser and dispatch changes land in plan tasks 2–4.
-sources:
-  decisions:
-    - .agentera/decisions.yaml#Decision-45
-    - .agentera/decisions.yaml#Decision-59
-    - .agentera/decisions.yaml#Decision-43
-  parent_contract: references/cli/agent-ready-state-contract.yaml
-  active_plan: .agentera/plan.yaml
-  implementation_entrypoint: the agentera CLI
-implementation_status: design_only
-non_goals:
-  - Do not implement parser, dispatch, or help-grouping changes in this contract task.
-  - Do not remove top-level aliases until the phased migration completes.
-  - Do not add capability workflow execution commands such as `agentera planera`.
-  - Do not expose top-level `agentera corpus`; corpus generation stays behind
-    `report refresh --consent local-history`.
-target_surface_summary: >-
-  Reduce the flat ~33 top-level verbs to ~18 by grouping routine state reads,
-  analytics, and maintainer gates under three audience namespaces while preserving
-  eleven top-level capability routing commands plus lifecycle commands.
-audience_tags:
-  agent: >-
-    Orientation, routine project-state reads, capability startup context, and
-    capability routing guidance the agent uses before raw artifact access.
-  user: >-
-    Install lifecycle, diagnostics, and privacy-gated analytics a human operator
-    runs without maintainer-only verification gates.
-  maintainer: >-
-    Validation, verification, lint, compaction, and repository gate checks used in
-    CI, hooks, and maintainer workflows.
-top_level_commands:
-  control_plane:
-    prime:
-      audience: [agent]
-      status: target_canonical
-      replaces: hej
-      default_behavior: >-
-        Composite orientation briefing currently owned by `hej` (installed-app gate,
-        health, plan, attention, next_action, source_contract). Static priming prose
-        moves to an explicit flag such as `--guidance` when still needed.
-      modes:
-        default: composite orientation briefing (formerly `hej`)
-        context: >-
-          `agentera prime --context <capability> --format json` — slim
-          `capability_context` startup capsule per Decision 59
-        dashboard: >-
-          `agentera prime --dashboard` / `--orientation` — orientation JSON mode
-          (provisional flag spelling)
-      skill_routing: >-
-        Bare `/agentera` and bare `hej` skill routes target `agentera prime`, not
-        a separate `hej` CLI command.
-      removed_from_top_level: hej
-    schema:
-      audience: [agent]
-      status: target_canonical
-      replaces: describe
-      owns:
-        - command tree discovery
-        - audience tag metadata
-        - filters and output format discovery
-        - structured output shape metadata
-        - field selection metadata
-        - Decision 43 slash-route alias descriptions
-        - artifact schema discovery
-        - linked contract section pointers
-      migration_alias:
-        command: describe
-        stderr: one-line deprecation naming `schema`
-        removal: after one minor alias release
-  capabilities:
-    audience: [agent]
-    status: preserved_top_level
-    count: 11
-    excludes: hej
-    commands:
-      - visionera
-      - resonera
-      - inspirera
-      - planera
-      - realisera
-      - optimera
-      - inspektera
-      - dokumentera
-      - profilera
-      - visualisera
-      - orkestrera
-    behavior: >-
-      Top-level capability-name commands emit routing guidance only. They do not
-      execute capability workflows. Capability startup JSON remains on
-      `agentera prime --context <capability> --format json`, not on capability tops.
-    non_goals:
-      - Do not demote capability tops to `prime --context` only.
-      - Do not add `agentera hej` back as a capability top.
-  lifecycle:
-    upgrade:
-      audience: [user]
-      status: preserved_top_level
-      notes: Stays top-level; no `setup` namespace wrapper.
-    doctor:
-      audience: [user]
-      status: preserved_top_level
-      notes: Agentera CLI/install/runtime self-check only; see parent contract `doctor`.
-audience_namespaces:
-  state:
-    audience: [agent]
-    status: target_canonical_namespace
-    purpose: Routine artifact reads and advanced artifact query.
-    subcommands:
-      plan:
-        canonical_shape: agentera state plan [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: plan
-      progress:
-        canonical_shape: agentera state progress [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: progress
-      health:
-        canonical_shape: agentera state health [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: health
-      todo:
-        canonical_shape: agentera state todo [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: todo
-      decisions:
-        canonical_shape: agentera state decisions [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: decisions
-      docs:
-        canonical_shape: agentera state docs [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: docs
-      objective:
-        canonical_shape: agentera state objective [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: objective
-      experiments:
-        canonical_shape: agentera state experiments [--format text|json|yaml] [--fields ...]
-        legacy_top_level_alias: experiments
-      query:
-        canonical_shape: agentera state query [--list-artifacts] [<artifact>] [--format ...]
-        legacy_top_level_alias: query
-        notes: Advanced artifact access; not the normal routine state interface.
-    decision_45_policy: >-
-      Decision 45 routine state command names (`plan`, `progress`, `health`, `todo`,
-      `decisions`, `docs`, `objective`, `experiments`, `query`) remain stable during
-      Phase 1–2 as top-level stderr-deprecation aliases that delegate to
-      `agentera state <name>`. Canonical namespace form is `state <name>`; JSON/YAML
-      envelopes and source_contract shapes are unchanged.
-  report:
-    audience: [user]
-    status: target_canonical_namespace
-    purpose: Privacy-gated usage analytics.
-    subcommands:
-      default_read:
-        canonical_shape: agentera report [--format text|json] [--project VALUE]
-        delegates_from: stats
-        behavior: Matches today's plain `agentera stats` read-only analytics.
-      refresh:
-        canonical_shape: >-
-          agentera report refresh [--dry-run] [--consent local-history]
-          [--project-root PATH] [--format text|json]
-        delegates_from: stats refresh
-        behavior: Matches today's `agentera stats refresh` including consent gates.
-      profile_glossary:
-        canonical_shape: >-
-          agentera report profile-glossary --input <file|-> [--dry-run]
-          --format json
-        delegates_from: null
-        behavior: >-
-          Applies one versioned personal glossary update request to the exact
-          PROFILE.md path supplied by Profile Full. Runs headlessly without a
-          project checkout; never discovers or reads project state or a project
-          glossary. Dry-run validates and computes the candidate without a write.
-    legacy_top_level_alias: stats
-    rejected_top_level: corpus
-    notes: >-
-      `agentera usage` and `agentera usage` remain backward-compatible
-      maintainer seams per AGENTS.md until separately classified; public user-facing
-      analytics and Profile's bounded personal-output implementation consolidate
-      under `report`.
-  check:
-    audience: [maintainer]
-    status: target_canonical_namespace
-    purpose: Validation, verification, lint, and repository compaction gates.
-    subcommands:
-      validate:
-        canonical_shape: agentera check validate <family> [target options]
-        delegates_from: validate
-        notes: Preserves current validate families including capability and artifact validation.
-      verify:
-        canonical_shape: agentera check verify <family> <target> [options]
-        delegates_from: verify
-        notes: Smoke and eval gate families unchanged.
-      lint:
-        canonical_shape: agentera check lint --artifact <ARTIFACT> [options]
-        delegates_from: lint
-      compact:
-        canonical_shape: agentera check compact [--project PATH] [--mode check|fix] [--format text|json]
-        delegates_from:
-          - compact
-        notes: >-
-          `check compact` owns check-only and fix modes. Top-level `gate` was
-          removed in Phase 3; artifact compaction budget checks remain on
-          `check compact`.
-    transitional_top_level_aliases:
-      - query
-      - compact
-      - verify
-      - stats
-      - lint
-      - validate
-help_grouping:
-  agent: [prime, state, schema, capabilities]
-  user: [upgrade, doctor, report]
-  maintainer: [check]
-prime_hej_schema_migration_boundary:
-  prime_absorbs_hej:
-    status: target
-    hej_cli: >-
-      Top-level `hej` is removed from the npm 3.x public parser and dispatch.
-      During Phase 1–2, `agentera hej` printed one stderr deprecation naming
-      `prime` and delegated; Phase 3 on the development channel rejects the
-      command with an unsupported-target envelope.
-    hej_skill_route: >-
-      Bare `hej` in the Agentera skill still routes to orientation, but the installed
-      CLI gate calls `agentera prime` and renders from that composite result.
-    prime_default: >-
-      Bare `agentera prime` emits the composite orientation briefing currently owned
-      by `hej`, not static priming-only prose. Static priming moves to `--guidance`
-      when retained.
-    prime_context_unchanged: >-
-      `agentera prime --context <capability> --format json` remains the sole supported
-      capability startup JSON seam per Decision 59; slim `capability_context` shape
-      and JSON budgets are unchanged.
-    doctor_default: >-
-      After migration, `agentera doctor --expect-command` defaults to `prime`, not
-      `hej`.
-  schema_replaces_describe:
-    status: target
-    canonical: agentera schema [--format json|yaml]
-    alias: >-
-      Top-level `describe` is removed from the npm 3.x public parser and dispatch.
-      During Phase 1–2, `agentera describe` printed one stderr deprecation naming
-      `schema` and delegated.
-    discovery_ownership: >-
-      `schema` owns runtime CLI/schema introspection formerly on `describe`, including
-      command tree, audience tags, artifact locations, and linked contract sections.
-      Capability startup contracts that reference discovery must point agents to
-      `agentera schema`, not `agentera describe`.
-decision_reconciliation:
-  decision_59:
-    prime_context_seam: >-
-      `prime --context` remains the capability startup seam. Top-level capability
-      names route to capability guidance; `prime` prepares the agent. Historical
-      `hej --capability-context` and `--context-profile full` paths stay removed.
-    prime_consolidation: >-
-      User direction consolidates dashboard/orientation into `prime` default briefing
-      rather than keeping bare `prime` as static-only priming plus a separate `hej`
-      dashboard owner.
-  decision_45:
-    routine_state_aliases: >-
-      Routine state names stay stable via top-level aliases during migration. Canonical
-      reads become `agentera state <name> list`; envelopes, field selection, and
-      source_contract semantics are unchanged.
-    slash_route_separation: >-
-      Decision 43 slash aliases remain excluded from the CLI command surface. The
-      shared word `plan` keeps three distinct meanings documented below.
-plan_routing_distinction:
-  slash_route:
-    invocation: /agentera plan
-    surface: Agentera skill slash route (Decision 43 primary alias)
-    routes_to: planera
-    meaning: >-
-      Request-to-capability routing — start or continue Planera planning work. This
-      is not a CLI command and does not read `.agentera/plan.yaml` by itself.
-  state_read:
-    invocation: agentera state plan list
-    legacy_alias: >-
-      Top-level `agentera plan` is capability routing, not a state-read alias;
-      use `agentera state plan list` for project state.
-    surface: CLI routine state read
-    meaning: >-
-      Read-only access to the active plan artifact summary, tasks, acceptance
-      criteria, evidence, and source_contract. Does not invoke Planera workflow
-      execution.
-  capability_top:
-    invocation: agentera plan
-    surface: CLI top-level capability routing command
-    meaning: >-
-      Emits plan capability routing guidance prose/schemas pointers. Does not replace
-      `state plan list` reads or `/agentera plan` slash routing. Capability startup JSON
-      remains `agentera prime --context plan --format json`.
-  agent_guidance: >-
-    Use `/agentera plan` when the user wants planning work routed to Planera; use
-    `agentera state plan list` when the agent needs plan artifact state; use
-    `agentera plan` for capability routing guidance; use
-    `agentera prime --context plan` for bounded plan startup context.
-migration_phases:
-  phase_1:
-    name: add_namespaces_and_delegate
-    actions:
-      - Add `state`, `report`, and `check` namespace parsers.
-      - Delegate to existing handlers without behavior change.
-      - Add `schema` top-level command delegating from `describe`.
-      - Make `prime` default emit composite orientation briefing.
-      - Keep legacy top-level names as stderr-deprecation aliases.
-  phase_2:
-    name: update_contracts_docs_hooks
-    actions:
-      - Update SKILL.md, AGENTS.md, hooks, CI, and semantic fixtures to prefer canonical forms.
-      - Emit audience tags and command tree from `agentera schema`.
-      - Record measurement evidence for JSON surface moves.
-  phase_3:
-    name: remove_deprecated_top_level_parsers
-    status: shipped_on_development_channel
-    actions:
-      - >-
-        Remove `hej`, public `describe`, and `gate` from top-level parser help
-        and dispatch on the npm 3.x CLI.
-      - >-
-        Remove routine-state top-level parsers (`plan`, `progress`, `health`,
-        `todo`, `decisions`, `docs`, `objective`, `experiments`) from help and
-        dispatch on the npm 3.x CLI.
-      - >-
-        Keep a transitional stderr-alias set (`validate`, `compact`, `verify`,
-        `stats`, `lint`, `query`) until post-cutover cleanup.
-alias_policy:
-  stderr_format: one-line deprecation naming the canonical command
-  delegation: forward to canonical handler with unchanged JSON/text envelopes
-  duration: one minor release minimum for hej, describe, and routine-state tops
-  forbidden:
-    - bundle-status compatibility alias (Decision 45 hard rename)
-    - adding Decision 43 slash aliases as CLI commands
-    - silent fallback without stderr during the alias period
-command_tree_target:
-  top_level_count: ~18
-  groups:
-    - prime [agent]
-    - schema [agent]
-    - visionera [agent]
-    - resonera [agent]
-    - inspirera [agent]
-    - planera [agent]
-    - realisera [agent]
-    - optimera [agent]
-    - inspektera [agent]
-    - dokumentera [agent]
-    - profilera [agent]
-    - visualisera [agent]
-    - orkestrera [agent]
-    - upgrade [user]
-    - doctor [user]
-    - state [agent]
-    - report [user]
-    - check [maintainer]
-
-removed_top_level_commands:
-  # Phase 3 on npm 3.x: removed from help and dispatch (unsupported_target)
-  - hej
-  - status
-  - describe
-  - gate
-  - progress
-  - health
-  - todo
-  - decisions
-  - docs
-  - objective
-  - experiments
-
-removed_top_level_corrections:
-  # Unsupported Phase 3 names return these canonical runnable corrections.
-  - { legacy: hej, canonical: prime }
-  - { legacy: status, canonical: prime }
-  - { legacy: describe, canonical: schema }
-  - { legacy: gate, canonical: "check compact" }
-  - { legacy: progress, canonical: "state progress" }
-  - { legacy: health, canonical: "state health" }
-  - { legacy: todo, canonical: "state todo" }
-  - { legacy: decisions, canonical: "state decisions" }
-  - { legacy: docs, canonical: "state docs" }
-  - { legacy: objective, canonical: "state objective" }
-  - { legacy: experiments, canonical: "state experiments" }
-
-transitional_stderr_aliases:
-  # Still delegate with one-line stderr deprecation on npm 3.x
-  - { legacy: query, canonical: "state query" }
-  - { legacy: compact, canonical: "check compact" }
-  - { legacy: verify, canonical: "check verify" }
-  - { legacy: stats, canonical: report }
-  - { legacy: lint, canonical: "check lint" }
-  - { legacy: validate, canonical: "check validate" }
-
-# Superseded by `removed_top_level_commands` and `transitional_stderr_aliases`
-# for npm 3.x Phase 3 (empty list retained for contract migration readers).
-deprecated_top_level_aliases: []

package/bundle/references/cli/bundle-skill-vocabulary.yaml

@@ -1,241 +0,0 @@
-schema_version: agentera.bundle_skill_vocabulary.v1
-status: active_authority
-purpose: >-
-  Classify surviving `bundle` and `SKILL.md` terminology so docs, package
-  metadata, tests, historical records, and compatibility
-  identifiers share one bounded vocabulary source without forcing mechanical
-  renames of shipped surfaces.
-sources:
-  prose:
-    - references/cli/vocabulary.md#bundle-and-skillmd-vocabulary
-scope:
-  includes:
-    - Current user-facing and diagnostic prose that names Agentera app files.
-    - Package and distribution metadata that names the suite package shape.
-    - Historical classification of retired runtime hook packaging prose and metadata.
-    - Historical references to the removed `bundle-status` command.
-    - Current references to `skills/agentera/SKILL.md`.
-  excludes:
-    - Routing and execution vocabulary collapse work.
-    - Capability instruction-file rename work.
-    - "`first_invocation_read` metadata or startup-read behavior."
-    - Objective state, decision satisfaction state, package publication, and installed app refreshes.
-compatibility_boundary: >-
-  Compatibility identifiers, package metadata names, fixture names, historical
-  records, and path-like references may keep `bundle` or `SKILL.md` when the
-  spelling is the contract. New conceptual prose should use the canonical
-  concept terms below.
-canonical_concept_order:
-  - agentera_app_files
-  - suite_package
-  - plugin_shipped_hooks
-  - removed_bundle_status_command
-  - agentera_routing_entry
-  - skill_entry_file
-canonical_concepts:
-  agentera_app_files:
-    definition: >-
-      Managed Agentera application files installed under the app files directory,
-      separate from user data in the Agentera directory.
-    allowed_terms:
-      - Agentera app files
-      - app files
-      - app files directory
-      - installed app
-      - managed app files
-    forbidden_ambiguous_shortcuts:
-      - bundle
-      - installed bundle
-      - bundle freshness
-      - bundle refresh
-      - durable bundle
-  suite_package:
-    definition: >-
-      The packaged distribution shape that ships the Agentera skill, CLI,
-      references, and package metadata as one suite artifact.
-    allowed_terms:
-      - suite package
-      - Agentera package
-      - packaged suite
-      - suite-bundle
-    forbidden_ambiguous_shortcuts:
-      - bundle
-      - single-bundle model
-      - bundled suite
-  retired_plugin_shipped_hooks:
-    definition: >-
-      Historical term for hooks shipped by retired v2 host-native packages.
-      Current Agentera packages ship no host-native hooks or plugin metadata.
-    allowed_terms:
-      - plugin-shipped hooks
-      - plugin-bundled hooks
-      - bundled hook metadata
-      - copied user hooks
-    forbidden_ambiguous_shortcuts:
-      - bundle hooks
-      - bundled hooks
-      - hook bundle
-  removed_bundle_status_command:
-    definition: >-
-      The removed legacy `agentera bundle-status` command name, preserved only
-      for historical release notes, migration evidence, and tests that prove it
-      remains unavailable.
-    allowed_terms:
-      - "removed `bundle-status` command"
-      - "legacy `agentera bundle-status` command"
-      - "historical `bundle-status` reference"
-    forbidden_ambiguous_shortcuts:
-      - bundle status
-      - bundle-status path
-      - bundle status command
-  agentera_routing_entry:
-    definition: >-
-      The v2 `skills/agentera/SKILL.md` routing entry that describes the Agentera
-      skill entry point, capability routing model, CLI-first state access, and
-      safety rails.
-    allowed_terms:
-      - Agentera routing entry point
-      - Agentera router
-      - routing layer
-      - "`skills/agentera/SKILL.md` routing entry"
-    forbidden_ambiguous_shortcuts:
-      - Agentera skill dispatcher
-      - SKILL.md
-      - master dispatcher
-      - skill dispatcher
-  skill_entry_file:
-    definition: >-
-      A concrete runtime skill entry file named `SKILL.md`, usually referenced
-      as a path or validation target rather than as a conceptual noun.
-    allowed_terms:
-      - skill entry file
-      - "`SKILL.md` file"
-      - "`skills/agentera/SKILL.md`"
-      - "`skills/*/SKILL.md`"
-    forbidden_ambiguous_shortcuts:
-      - SKILL.md
-      - skill file
-      - skill entry
-classification_order:
-  - canonical_concept
-  - compatibility_identifier
-  - path_like_reference
-  - package_metadata
-  - historical_record
-  - fixture_only
-  - generic_plain_language
-  - ambiguous_current_prose
-classification_rules:
-  canonical_concept:
-    meaning: Usage matches one of the canonical concepts and uses an allowed term.
-    action: Keep and prefer in new current prose.
-  compatibility_identifier:
-    meaning: The spelling is a shipped field, command flag, file name, code identifier, or parseable label.
-    action: Preserve until an explicit migration exists.
-  path_like_reference:
-    meaning: The occurrence is a literal file path, glob, manifest path, fixture path, or code path.
-    action: Preserve the concrete path spelling.
-  package_metadata:
-    meaning: The occurrence is a concrete package metadata value or installed package layout name.
-    action: Preserve unless package metadata migration is explicitly in scope.
-  historical_record:
-    meaning: The occurrence is in changelog, progress, decision, archived plan, migration history, or release evidence.
-    action: Do not rewrite solely for vocabulary cleanup; qualify when current prose interprets it.
-  fixture_only:
-    meaning: The occurrence is test fixture input, expected compatibility output, or stale-path regression data.
-    action: Preserve when the test proves compatibility or rejection behavior.
-  generic_plain_language:
-    meaning: The occurrence is ordinary English unrelated to Agentera app files, package shape, hooks, commands, or skill entries.
-    action: Allowed, but prefer object-specific terms when risk is high.
-  ambiguous_current_prose:
-    meaning: The occurrence uses bare `bundle` or bare `SKILL.md` as a conceptual noun in current user-facing prose.
-    action: Replace or qualify with the relevant canonical concept term.
-focused_scan:
-  allowed_classifications:
-    - canonical
-    - compatibility-preserved
-    - migration-only
-    - historical
-    - fixture-only
-    - generic
-  paths:
-    - AGENTS.md
-    - README.md
-    - references/cli/vocabulary.md
-    - (retired maintainer measurement tool)
-    - skills/agentera/SKILL.md
-    - skills/agentera/capabilities/hej/schemas/triggers.yaml
-    - packages/cli/src/capabilities/resonera/instructions.ts
-    - tests/test_cross_capability.py
-    - tests/test_resonera_capability.py
-    - tests/test_runtime_adapters.py
-  allowed_occurrences:
-    - path: ^AGENTS\.md$
-      text: skills/agentera/SKILL\.md|Agentera routing entry point
-      classification: canonical
-      reason: AGENTS guidance names the concrete Agentera routing entry point.
-    - path: ^README\.md$
-      text: skills/agentera/SKILL\.md|Agentera routing entry point
-      classification: canonical
-      reason: README names the canonical routing entry point and concrete linked path.
-    - path: ^references/cli/vocabulary\.md$
-      text: references/cli/bundle-skill-vocabulary\.yaml|Bundle and SKILL\.md vocabulary
-      classification: canonical
-      reason: Vocabulary docs delegate this exact concept family to this authority.
-    - path: ^references/cli/vocabulary\.md$
-      text: Agentera app files need repair|bundle freshness|bundle refresh|required repair Agentera app files|install status check failed
-      classification: historical
-      reason: Decision 44 replacement tables preserve deprecated bundle wording as historical examples.
-    - path: ^references/cli/vocabulary\.md$
-      text: skills/agentera/SKILL\.md|SKILL\.md`
-      classification: canonical
-      reason: Vocabulary docs use concrete skill entry file paths and source-index references.
-    - path: ^references/cli/vocabulary\.md$
-      text: --only bundle|\.agentera-bundle\.json|bundle\.status|activeBundleRoot|bundle-status
-      classification: migration-only
-      reason: Vocabulary docs classify retired v2 identifiers for migration evidence and released history only.
-    - path: ^scripts/measure_token_payload\.py$
-      text: 'v1 baseline: all 12 v1 SKILL\.md files|skill_root / "SKILL\.md"'
-      classification: historical
-      reason: Token payload measurement preserves the historical v1 SKILL.md baseline and concrete path construction.
-    - path: ^skills/agentera/SKILL\.md$
-      text: \.agentera-bundle\.json|bundle\.status|bundle\.dryRunCommand
-      classification: compatibility-preserved
-      reason: The routing entry documents CLI-provided compatibility fields and marker files that still exist.
-    - path: ^skills/agentera/SKILL\.md$
-      text: SKILL\.md\s+# This file
-      classification: canonical
-      reason: The directory listing names the actual Agentera routing entry file.
-    - path: ^tests/test_cross_capability\.py$
-      text: SKILL_MD_PATH|test_master_bundle_health_gate|bundle\.status|bundle\.dryRunCommand
-      classification: fixture-only
-      reason: Cross-capability tests assert compatibility wording and historical test names.
-    - path: ^tests/test_runtime_adapters\.py$
-      text: .
-      classification: fixture-only
-      reason: Runtime adapter tests use fixture paths, expected diagnostics, package metadata, and compatibility test class names.
-migration_identifiers:
-  bundle:
-    - .agentera-bundle.json
-    - bundle.status
-    - activeBundleRoot
-    - "--only bundle"
-    - bundle.dryRunCommand
-  skill_entry_file:
-    - skills/agentera/SKILL.md
-    - skills/*/SKILL.md
-    - SKILL.md
-package_metadata_values:
-  - suite-bundle
-  - agentera/bundle
-  - bundle-only enhancements
-historical_terms:
-  - agentera bundle-status
-  - bundle-status
-  - single-bundle model
-  - Agentera skill dispatcher
-docs_delegation:
-  document: references/cli/vocabulary.md
-  required_anchor: Bundle and SKILL.md vocabulary
-  authority_path: references/cli/bundle-skill-vocabulary.yaml
-  must_not_duplicate_large_table: true