agentera 3.0.0-dev.23 → 3.0.0-dev.26

package/bundle/references/cli/agent-ready-state-contract.yaml

@@ -70,21 +70,21 @@ doctor:
   compatibility_alias: forbidden
   owns:
     - Agentera CLI self-check status
-    - installed bundle status
-    - install-root status
-    - runtime adapter availability and configuration diagnostics
-    - hook, package, and schema availability checks when implemented
+    - installed app and install-root status
+    - canonical shared-skill diagnosis
+    - project integration and project-state migration diagnostics
+    - bounded offline smoke checks when requested
   excludes:
     - project artifact health
     - codebase quality audit findings
     - inspektera architecture, test, dependency, or documentation audit output
   adjacent_surfaces:
     codebase_audit: /agentera audit routes to inspektera
-    setup_specific_diagnostics: packages/cli/src/setup/doctor.ts
   rationale: >-
     Decision 45 rejects `bundle-status` as too narrow and rejects an alias for
-     release-clean vocabulary; `doctor` is the CLI/install/runtime self-check
-     vocabulary, while artifact health and codebase audits remain separate concerns.
+     release-clean vocabulary; `doctor` is the CLI, app, shared-skill, and project
+     integration self-check vocabulary, while artifact health and codebase audits
+     remain separate concerns.
 schema:
   status: implemented_runtime_introspection
   command: schema
@@ -237,7 +237,7 @@ structured_output:
         - project_integration
         - attention
         - history
-        - runtime_lifecycle
+        - shared_skill
         - decision_attention
         - next_action
         - orchestration_context
@@ -332,7 +332,7 @@ structured_output:
             derives from the same `_decision_context_entry` and
              `_decision_satisfaction_context` semantics as bounded `agentera state
              decisions list --limit 20 --format json` plus exact `state decisions
-             get --number N`, never infers satisfaction, never mutates `.agentera/decisions.yaml`,
+             get --id ID`, never infers satisfaction, never mutates decision entities,
             keeps top-level attention bounded, and must not change `next_action`
             routing priority.
           evidence_context_target_contract: evidence_context_target_contract
@@ -491,13 +491,13 @@ evidence_context_target_contract:
         fallback: none when complete_for_plan_artifact is true
       - family: progress_verification
         source: agentera state progress list --limit 20 --format json latest verification
-        fallback: agentera state progress get --number N --format json
+        fallback: agentera state progress get --id ID --format json
       - family: docs_state
         source: agentera state docs --format json summary and entries
         fallback: agentera state docs --format json
       - family: health_state
         source: agentera state health list --limit 20 --format json latest audit
-        fallback: agentera state health get --number N --format json
+        fallback: agentera state health get --id ID --format json
       - family: todo_state
         source: agentera state todo --format json known issues and source-contract TODOs
         fallback: agentera state todo --format json
@@ -575,7 +575,7 @@ field_selection:
         - project_integration
         - attention
         - history
-        - runtime_lifecycle
+        - shared_skill
         - decision_attention
         - next_action
         - orchestration_context

package/bundle/references/cli/app-lifecycle-vocabulary.yaml

@@ -25,10 +25,9 @@ scope:
     - Update channel names, dist-tag resolution, and override keys.
     - General prose outside app lifecycle metadata.
 compatibility_boundary: >-
-  Compatibility identifiers such as `.agentera-bundle.json`, `bundle.status`,
-  `activeBundleRoot`, and `--only bundle` may remain until an explicit migration
-  exists. They do not make bundle/fresh/stale/refresh/fixed canonical app
-  lifecycle status vocabulary.
+  Retired v2 identifiers such as `.agentera-bundle.json`, `bundle.status`,
+  `activeBundleRoot`, and `--only bundle` may remain only in migration readers,
+  fixtures, and released history. They are not current app lifecycle vocabulary.
 canonical_status_order:
   - up_to_date
   - outdated

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

@@ -12,7 +12,7 @@ scope:
   includes:
     - Current user-facing and diagnostic prose that names Agentera app files.
     - Package and distribution metadata that names the suite package shape.
-    - Runtime hook packaging prose and metadata for plugin-shipped hooks.
+    - 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:
@@ -52,8 +52,7 @@ canonical_concepts:
   suite_package:
     definition: >-
       The packaged distribution shape that ships the Agentera skill, CLI,
-      scripts, hooks, references, runtime descriptors, and package metadata as
-      one suite artifact.
+      references, and package metadata as one suite artifact.
     allowed_terms:
       - suite package
       - Agentera package
@@ -63,10 +62,10 @@ canonical_concepts:
       - bundle
       - single-bundle model
       - bundled suite
-  plugin_shipped_hooks:
+  retired_plugin_shipped_hooks:
     definition: >-
-      Hooks that are shipped by active runtime plugin package surfaces such as
-      Codex, OpenCode, Cursor, or GitHub plugin metadata.
+      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
@@ -155,6 +154,7 @@ focused_scan:
   allowed_classifications:
     - canonical
     - compatibility-preserved
+    - migration-only
     - historical
     - fixture-only
     - generic
@@ -162,7 +162,6 @@ focused_scan:
     - AGENTS.md
     - README.md
     - references/cli/vocabulary.md
-    - references/adapters/opencode.md
     - (retired maintainer measurement tool)
     - skills/agentera/SKILL.md
     - skills/agentera/capabilities/hej/schemas/triggers.yaml
@@ -193,16 +192,8 @@ focused_scan:
       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: compatibility-preserved
-      reason: Vocabulary docs preserve shipped compatibility identifiers and removed command references.
-    - path: ^references/adapters/opencode\.md$
-      text: bundled Agentera dashboard path|bundled `agentera` skill|bundled Agentera
-      classification: generic
-      reason: OpenCode adapter prose uses bundled in the ordinary package-shipping sense, not as Agentera app-file terminology.
-    - path: ^references/adapters/opencode\.md$
-      text: SKILL\.md files|<name>/SKILL\.md|skills/\*/SKILL\.md|skills/agentera/SKILL\.md
-      classification: compatibility-preserved
-      reason: OpenCode adapter prose documents concrete runtime skill entry file paths.
+      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
@@ -223,7 +214,7 @@ focused_scan:
       text: .
       classification: fixture-only
       reason: Runtime adapter tests use fixture paths, expected diagnostics, package metadata, and compatibility test class names.
-compatibility_identifiers:
+migration_identifiers:
   bundle:
     - .agentera-bundle.json
     - bundle.status

package/bundle/references/cli/capability-tool-classification.yaml

@@ -1,7 +1,7 @@
 # Capability tool classification authority
 # Defines which tools each capability subagent needs to fulfill its purpose.
-# Consumed by: descriptor validation, regression tests, runtime adapter docs.
-# Source of truth for per-capability tool requirements across all runtimes.
+# Consumed by shared-skill worker metadata validation and regression tests.
+# Hosts provide and enforce their own tool surfaces; Agentera ships no native adapter.
 
 classification:
   mutation_capable:

package/bundle/references/cli/prime-consumer-compatibility.yaml

@@ -22,34 +22,6 @@ exclusions:
 # Tasks 2-4 MUST keep every consumed field resolvable from a declared surface.
 # ---------------------------------------------------------------------------
 consumers:
-  - id: opencode_compaction_context
-    startup_command: agentera prime --format json
-    evidence: .opencode/plugins/agentera.js:502-517
-    consumed_fields:
-      - mode
-      - profile.status
-      - profile
-      - health.grade
-      - health.trajectory
-      - health
-      - issues
-      - plan
-      - plan.exists
-      - plan.status
-      - plan.title
-      - plan.first_pending.name
-      - progress
-      - progress.latest
-      - progress.latest.number
-      - progress.latest.what
-      - progress.latest.next
-      - next_action
-      - next_action.object
-      - attention
-    notes: >-
-      Reads the deprecated `issues` alias instead of `todo` (lines 480-486).
-      This is the only documented runtime consumer of the deprecated alias, so
-      `issues` is transition-required until the stable cut.
   - id: status_dashboard_renderer
     startup_command: agentera prime --context status --format json
     evidence: skills/agentera/SKILL.md:68
@@ -75,43 +47,35 @@ consumers:
       through the named command in the status context, never by raw artifact read.
   - id: capability_context_dispatcher
     startup_command: agentera prime --context <capability> --format json
-    evidence: .opencode/agents/agentera.md:12
-    alt_evidence: .cursor/agents/agentera.md:7
-    runtime_evidence: packages/cli/src/cli/capabilityContext/startup.ts:250
+    evidence: packages/cli/src/cli/capabilityContext/startup.ts:250
+    skill_evidence: skills/agentera/SKILL.md:68-103
     consumed_fields:
       - command
       - status
       - capability_context
       - capability_context.instructions
     notes: >-
-      Per-capability startup capsule. The runtime emits
+      Per-capability startup capsule. The CLI emits
       `capability_context.instructions` (the capability's instructions module),
-      not `prose`. The agent descriptors (.opencode/agents/agentera.md and
-      .cursor/agents/agentera.md) formerly documented a `prose` field that the
-      v3 runtime never emits; they were reconciled to
-      `capability_context.instructions` to match
-      packages/cli/src/cli/capabilityContext/startup.ts:250 and
-      skills/agentera/SKILL.md (lines 68, 103), which already documented
-      `capability_context.instructions`. This consumer governs the `--context`
+      not `prose`; the shared skill consumes that field directly. This consumer
+      governs the `--context`
       surface, not the bare briefing; the bounded decision brief (Task 3) must
       not break the `--context` capsule. Executable fixture proves the emitted
       payload contains `capability_context.instructions` and NOT `prose`.
   - id: packaging_distribution_gate
     startup_command: agentera prime --format json
-    evidence: docs/packaging/v3-packaging.md:130-139
+    evidence: packages/cli/test/packaging/packageVerification.test.ts
     consumed_fields:
       - command
       - status
       - app_home
       - app_home.source
     notes: >-
-      Distribution/packaging verification matrix consumer. The Prime gate
-      (line 136) asserts `command: "prime"`, `status: "ok"`, and that
-      `app_home.source` reflects resolution; the Bun smoke gate (line 139)
-      asserts the published single binary runs `agentera prime --format json`
-      and exits 0 with the same JSON shape. Tasks 2-4 must keep the published
-      prime JSON shape stable so packaged binaries and fresh-cache npx gates
-      keep passing. Not a dashboard consumer; does not read state families.
+      Distribution-boundary consumer. The one extracted-package conjunction
+      asserts `command: "prime"`, `status: "ok"`, and that `app_home.source`
+      reflects resolution after the packed upgrade path. Tasks 2-4 must keep
+      the published prime JSON shape stable so fresh-cache npx gates keep
+      passing. Not a dashboard consumer; does not read state families.
   - id: json_output_surface_manifest
     startup_command: agentera prime [ --dashboard | --context <capability> ] --format json
     evidence: scripts/json_output_surface_manifest.yaml:47-161
@@ -136,9 +100,8 @@ consumers:
       from the retired `prose` field to the v3 `capability_context.instructions`
       field after the second Task 1 evaluation found this guidance was the one
       remaining live consumer contradiction. Runtime authority
-      (capabilityContext/startup.ts:250), SKILL.md (lines 68, 103), and the
-      agent descriptors (.opencode/agents/agentera.md, .cursor/agents/agentera.md)
-      all already used `capability_context.instructions`. The
+      (capabilityContext/startup.ts:250) and SKILL.md (lines 68, 103) both use
+      `capability_context.instructions`. The
       `documentation_drift` guard below prevents this guidance from drifting
       back to `prose`; it does not execute a prime command.
 
@@ -154,7 +117,7 @@ consumers:
 # and kept until the 3.0.0 stable cut; it is excluded only from the canonical
 # advertised `source_contract.fields` set (one canonical representation — `todo`
 # is canonical). It is NOT selector-only: it ships in the default bare briefing
-# for the opencode_compaction_context consumer that still reads it.
+# only as bounded CLI transition compatibility.
 # ---------------------------------------------------------------------------
 field_authorities:
   - id: orientation_output_emission
@@ -194,7 +157,7 @@ field_authorities:
     notes: >-
       Reconciled by Task 2: both hej.fields lists now mirror the canonical
       27-field set (retired `bundle` dropped; app, app_home, project_integration,
-      runtime_lifecycle, and history added).
+      shared_skill, project_integration, and history added).
 
 # ---------------------------------------------------------------------------
 # Field classification. Every field proposed for omission is classified with a
@@ -264,8 +227,8 @@ field_classification:
   - field: project_integration
     status: required
     rationale: >-
-      Status routing consumes the recommendation and aggregate lifecycle state;
-      the bounded brief retains the routing projection even when no upgrade
+      Status routing consumes the app and project-state recommendation; the
+      bounded brief retains that routing projection even when no upgrade
       recommendation is active.
   - field: attention
     status: required
@@ -276,11 +239,9 @@ field_classification:
       Startup history. The bounded brief retains counts and named retrieval
       pointers while omitting entry detail; explicit state list/get commands
       recover the current history.
-  - field: runtime_lifecycle
-    status: conditional
-    rationale: >-
-      Diagnostic. Plan constraint: unrelated lifecycle diagnostics are omitted
-      unless status declares them necessary for the current brief (Task 4).
+  - field: shared_skill
+    status: required
+    rationale: Canonical shared-skill path and read-only diagnosis.
   - field: decision_attention
     status: conditional
     rationale: Null unless returned decisions require satisfaction review.
@@ -326,10 +287,9 @@ field_classification:
   - field: issues
     status: deprecated_transition
     rationale: >-
-      Deprecated alias of `todo`. opencode_compaction_context reads it
-      (.opencode/plugins/agentera.js:480-486). Removable at the 3.0.0 stable cut
-      only; tracked in TODO.md [fix:3.0.0]. Tasks 2-4 must keep the alias and
-      the stderr deprecation warning.
+      Deprecated alias of `todo`. No current consumer in this inventory reads
+      it; the alias remains only as bounded CLI transition compatibility until
+      its owning contract removes it.
   - field: bundle
     status: retired
     rationale: >-
@@ -369,9 +329,9 @@ public_output_policy:
     separate bare-prime call or raw artifact read. The `--context` capsule
     contract (command/status/capability_context) is unchanged. The status
     capsule puts the canonical Task 3 projection at
-    `capability_context.context.status_context`; unrelated per-runtime
-    lifecycle diagnostics are omitted while aggregate release-blocking state
-    remains available for routing.
+    `capability_context.context.status_context`; app/project integration and
+    shared-skill diagnosis remain available for routing while unrelated detail
+    is omitted.
   status_context_contract:
     startup_command: agentera prime --context status --format json
     state_path: capability_context.context.status_context
@@ -474,7 +434,7 @@ default_emission_omission_contract:
       only; diagnostics measured separately on stderr.
     retained_top_level_fields: >-
       Every field in never_omitted plus command, status, app_home, app, mode,
-      history, runtime_lifecycle, project_integration, decision_attention, and
+      history, shared_skill, project_integration, decision_attention, and
       the bespoke context pointers (kept null on the bare surface). The
       conditional v1_migration/docs/objective are retained when active (see
       omitted_when_default). issues ships as the deprecated transition alias.
@@ -491,9 +451,6 @@ default_emission_omission_contract:
       - field: history.{progress,decisions,health}.entries
         reason: startup_history_entries
         recovery: agentera state <artifact> list --limit 20 --format json
-      - field: runtime_lifecycle.runtimes
-        reason: lifecycle_runtime_detail
-        recovery: agentera upgrade --dry-run --format json
       - field: project_integration.phases
         reason: phase_blockers
         recovery: agentera doctor --format json
@@ -546,7 +503,7 @@ declared_available_fields:
   - project_integration
   - attention
   - history
-  - runtime_lifecycle
+  - shared_skill
   - decision_attention
   - next_action
   - orchestration_context
@@ -560,33 +517,6 @@ declared_available_fields:
   - issues
 fixtures:
   pass:
-    - consumer: opencode_compaction_context
-      executable_command: agentera prime --format json
-      depends_on:
-        - mode
-        - profile
-        - health
-        - issues
-        - plan
-        - progress
-        - next_action
-        - attention
-      nested_fields:
-        - profile.status
-        - next_action.object
-      conditional_nested_fields:
-        - path: health.grade
-          present_when: health.exists
-        - path: health.trajectory
-          present_when: health.exists
-        - path: plan.first_pending.name
-          present_when: plan.first_pending
-        - path: progress.latest.number
-          present_when: progress.latest
-        - path: progress.latest.what
-          present_when: progress.latest
-        - path: progress.latest.next
-          present_when: progress.latest
     - consumer: status_dashboard_renderer
       executable_command: agentera prime --context status --format json
       depends_on:

package/bundle/references/cli/routing-execution-vocabulary.yaml

@@ -2,7 +2,7 @@ schema_version: agentera.routing_execution_vocabulary.v1
 status: active_authority
 purpose: >-
   Define routing and execution vocabulary boundaries so request routing, next-action
-  recommendation, Orkestrera task assignment, worker launch, runtime support, and
+  recommendation, Orkestrera task assignment, worker launch, host-provided worker support, and
   worker-safety Git commits stay distinct without forcing mechanical renames of
   shipped compatibility identifiers or historical evidence.
 sources:
@@ -14,7 +14,7 @@ scope:
     - Hej and capability next-action recommendations that wait for confirmation.
     - Orkestrera assignment of approved plan work to worker capabilities.
     - Realisera and Optimera launch of runtime workers.
-    - Runtime subagent support mechanisms and compatibility identifiers.
+    - Host-provided worker mechanisms without Agentera-owned runtime integration.
     - Git commit safety language before spawning isolated worker execution.
   excludes:
     - Broad current-prose replacement across capability instructions.
@@ -96,8 +96,8 @@ canonical_concepts:
       - launch substrate
   runtime_subagent_support:
     definition: >-
-      Runtime-specific support that lets Agentera use a host's subagent surface,
-      descriptor model, or equivalent worker mechanism.
+      A worker mechanism supplied by the coding host. Agentera may request a
+      worker but ships no host-specific descriptor, adapter, plugin, or hook.
     preferred_terms:
       - subagent mechanism
       - runtime subagent mechanism
@@ -167,7 +167,6 @@ focused_scan:
   paths:
     - AGENTS.md
     - references/cli/vocabulary.md
-    - references/adapters/runtime-feature-parity.md
     - (retired maintainer measurement tool)
     - skills/agentera/SKILL.md
     - skills/agentera/references/contract.md
@@ -198,10 +197,6 @@ focused_scan:
       text: subagent_dispatch|fixture names
       classification: compatibility-preserved
       reason: Routing vocabulary docs preserve explicit compatibility identifiers and fixture terminology.
-    - path: ^references/adapters/runtime-feature-parity\.md$
-      text: prompt rewrite router|Subagent Dispatch|Dispatch surface|Capability dispatch|subagent dispatch
-      classification: compatibility-preserved
-      reason: Runtime parity docs name concrete host and compatibility surfaces around descriptor dispatch support.
     - path: ^scripts/measure_token_payload\.py$
       text: static dispatch payload|Agentera router
       classification: historical
@@ -238,20 +233,7 @@ focused_scan:
       text: '`dispatch`: invoke another capability autonomously|`chain`: dispatch multiple capabilities autonomously|In orkestrera only, `dispatch` and `chain` are autonomous'
       classification: fixture-only
       reason: Skill dispatch contract tests assert the canonical Orkestrera dispatch reservation.
-    - path: ^tests/test_runtime_adapters\.py$
-      text: opencode bare-hej router|routeBareHejMessage|subagent_dispatch
-      classification: fixture-only
-      reason: Runtime adapter tests assert plugin routing helpers and compatibility identifier fixtures.
-    - path: ^tests/test_runtime_adapter_registry\.py$
-      text: subagent_dispatch
-      classification: code-identifier
-      reason: Runtime adapter registry tests preserve the shipped subagent_dispatch field name.
 compatibility_identifiers:
-  runtime_adapter:
-    - subagent_dispatch
-    - RuntimeAdapter.subagent_dispatch
-    - subagent_dispatch.supported
-    - subagent_dispatch.group
   route_aliases:
     - ROUTE_ALIASES
     - primary_aliases

package/bundle/references/cli/update-channels.yaml

@@ -45,7 +45,8 @@ channels:
         supported 2.x line until you explicitly opt in through npm.
       guide_url: >-
         https://github.com/jgabor/agentera/blob/main/UPGRADE.md#upgrading-v2-to-v3-development-channel-irreversible
-      preview_command: npx -y agentera@next upgrade --dry-run --channel development
+      preview_command: npx -y agentera@next upgrade --channel development --project "$PWD" --dry-run
+      apply_command: npx -y agentera@next upgrade --channel development --project "$PWD" --yes
       irreversible_advisory: >-
         Forward migration to the successor line is one-way; return to the prior
         Python support line is permanently unsupported.
@@ -75,7 +76,8 @@ channels:
         The v3 successor line is npm-only; opt in to v2→v3 migration through npx @next.
       guide_url: >-
         https://github.com/jgabor/agentera/blob/main/UPGRADE.md#upgrading-v2-to-v3-development-channel-irreversible
-      preview_command: npx -y agentera@next upgrade --dry-run --channel development
+      preview_command: npx -y agentera@next upgrade --channel development --project "$PWD" --dry-run
+      apply_command: npx -y agentera@next upgrade --channel development --project "$PWD" --yes
       irreversible_advisory: >-
         Forward migration to the v3 line is one-way; return to the prior
         Python support line is permanently unsupported.

package/bundle/references/cli/upgrade-repair-wording.md

@@ -1,34 +1,14 @@
-# Upgrade repair wording — v3 cursor agent skip
+# Upgrade repair wording
 
-When `agentera upgrade --runtime cursor` (or a full runtime phase) runs against a
-**project** directory, managed `.cursor/agents/*.md` descriptors are normally
-copied from the active app-home bundle. On a **v3 capability-surface** project
-that signal is suppressed so D65 `prime --context` bodies are not regressed to
-the retired `instructions.md` read path.
+## Runtime migration boundary
 
-## v3 surface probe
+Recognized v2-to-v3 project migration rewires existing Agentera v2 hook
+configurations to the npm CLI and retires only proven Agentera-owned legacy hook
+files. It does not copy or refresh plugins, agents, commands, or skill links.
 
-Treat the project as v3 when **all twelve** instruction modules exist:
-
-`packages/cli/src/capabilities/<name>/instructions.ts`
-
-for every routed capability (`status`, `vision`, `discuss`, `research`,
-`plan`, `build`, `optimize`, `audit`, `document`, `profile`,
-`design`, `orchestrate`).
-
-If any module is missing, preserve v2 upgrade behavior (copy/refresh managed
-agents from the bundle).
-
-## Orchestrator behavior
-
-| Orchestrator | Branch | Behavior |
-| --- | --- | --- |
-| TypeScript (`packages/cli/src/upgrade/runtimeMigration.ts`) | `feat/v3` | On v3 probe match, emit `skipped` `copy-agent` items for in-tree `.cursor/agents/` instead of copying from the bundle. |
-| Python (`scripts/agentera_upgrade.py`) | `main` (stable) | Same probe before the cursor agent copy loop; do not schedule `copy-agent` targets under the project when the probe matches. Backport per the both-branch pattern. |
-
-## User-visible skip message
-
-`v3 capability instruction modules present; in-tree .cursor/agents/ uses prime --context and is not overwritten`
+Runtime lifecycle installation and remediation are separate. Apply requires an
+explicit `--runtime` selector and `--yes`; declared ownership, collision
+remediation, and convergent retry behavior remain governed by `UPGRADE.md`.
 
 ## v2 install track successor surfacing (#32)
 

package/bundle/references/cli/v3-handoff-manifest.schema.yaml

@@ -47,9 +47,8 @@ required_top_level_fields:
     items:
       type: string
     description: >-
-      Runtime adapter ids (references/adapters/runtime-adapter-registry.yaml)
-      that the v2 install actively uses — runtimes whose setup doctor status is
-      pass at write time.
+      Historical runtime adapter ids that the v2 install actively used at handoff.
+      The v3 reader treats these as migration evidence, not active runtime inventory.
 user_data_inventory_catalog:
   - id: benchmarks
     relative_path: benchmarks