agentera 3.0.0-dev.0 → 3.0.0-dev.10

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

@@ -229,7 +229,7 @@ structured_output:
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
@@ -282,10 +282,10 @@ structured_output:
             contract can summarize planning levels, step markers, CLI-first
             orientation, raw plan artifact boundaries, full-plan review/self-audit
             requirements, handoff expectations, and the Planera prose authority
-            boundary without reading `planera/instructions.md` at runtime. It must
-            not introduce `agentera planera`, new top-level commands, or hidden
-            capability-name aliases; `agentera schema` owns runtime/schema
-            introspection rather than a capability workflow payload.
+            boundary without reading `packages/cli/src/capabilities/planera/instructions.ts`
+            at runtime. It must not introduce `agentera planera`, new top-level
+            commands, or hidden capability-name aliases; `agentera schema` owns
+            runtime/schema introspection rather than a capability workflow payload.
           orchestration_context_semantics: >-
             `agentera prime --context orkestrera --format json` may include
             orchestration_context with dependency-ready tasks, blocked task reasons,
@@ -465,7 +465,7 @@ evidence_context_target_contract:
         verified_field: header.status=complete
       - reason: Inspektera prose and schemas are validated directly; complete evidence_context covers normal evaluation startup without raw plan/progress/docs/health/TODO/decisions reads.
         paths:
-          - skills/agentera/capabilities/inspektera/instructions.md
+          - packages/cli/src/capabilities/inspektera/instructions.ts
           - skills/agentera/capabilities/inspektera/schemas/artifacts.yaml
           - skills/agentera/capabilities/inspektera/schemas/validation.yaml
         raw_artifact_reads_required_for_startup: false
@@ -589,7 +589,7 @@ field_selection:
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
@@ -755,11 +755,13 @@ verify_namespace:
   rejected_umbrella_command: smoke
   purpose: >-
     Define the supported `agentera verify` namespace so agents can run or inspect
-    smoke and eval gates through one discoverable verification surface without
-    guessing direct script names or unsupported capability-name CLI commands.
+    eval gates through one discoverable verification surface without guessing direct
+    script names or unsupported capability-name CLI commands.
   namespace_rationale: >-
     `agentera verify` is the public command for the evaluation gates (skills and
-    semantic). The smoke-check family was retired in the self-contained package.
+    semantic) on the npm self-contained CLI. The smoke-check family is retired on
+    @next; run smoke maintainer harnesses on the stable Python line with
+    `uvx --from git+https://github.com/jgabor/agentera@main agentera check verify smoke installed-skills`.
   command_shape: agentera verify <family> <target> [--format text|json] [target options]
   supported_gate_families:
     eval:
@@ -810,9 +812,11 @@ verify_namespace:
       - skipped
   invalid_input_behavior:
     family_error: >-
-      Unknown verify families must exit nonzero, list valid families `smoke` and
-      `eval`, show `agentera verify <family> <target> [--format text|json]`, and
-      include concrete examples for one smoke target and one eval target.
+      Unknown verify families must exit nonzero, list valid family `eval`, show
+      `agentera verify <family> <target> [--format text|json]`, and include a
+      concrete eval example. Requests for the retired `smoke` family must exit
+      nonzero with explicit npm-retired guidance pointing to eval verify or the
+      stable Python maintainer path.
     target_error: >-
       Unknown targets must exit nonzero, list valid targets for the selected family,
       show the correct family syntax, and include one concrete example for that family.
@@ -831,18 +835,17 @@ verify_namespace:
     - >-
       `agentera verify eval semantic` remains callable directly with fixture path arguments
       and existing offline semantic fixture behavior.
-      offline default behavior plus the explicit `--real-npx` opt-in path.
-      default behavior and explicit `--live`/`--yes` live-host opt-in behavior.
-      observable smoke-check behavior, including current non-argparse `--help` behavior.
-      observable local bootstrap diagnostics and failure behavior.
+    - >-
+      Retired `smoke` verify requests on the npm self-contained CLI must fail with
+      bounded guidance instead of invoking Python smoke harnesses.
   non_goals:
     - Do not add unsupported capability-name CLI commands such as `agentera realisera` or `agentera orkestrera`.
     - Do not reintroduce the retired smoke gate-family.
     - Do not implement D48 `validate`, `corpus`, or `usage` work.
     - Do not run live network, installed-app mutation, profile refresh, publication, push, tag, or package-update flows as part of this contract definition.
   evidence_sources:
-    - agentera --help exposes the `verify` namespace and safe smoke/eval examples.
-    - the verify vitest tests (packages/cli/test/cli/verify.test.ts) covers smoke success, eval success, text output, JSON output, invalid input feedback, safety boundaries, and preserved direct-script compatibility.
+    - agentera --help exposes the `verify` namespace and eval examples only on npm @next.
+    - the verify vitest tests (packages/cli/test/cli/verify.test.ts) cover eval success, smoke retirement, text output, JSON output, invalid input feedback, safety boundaries, and preserved direct-script compatibility.
     - agentera verify eval skills --help defines `--skill`, `--dry-run`, `--parallel`, `--timeout`, and `--runtime`.
     - agentera verify eval semantic --help defines fixture path inputs for offline semantic evaluation.
 usage_namespace:
@@ -877,7 +880,7 @@ usage_namespace:
       behavior: >-
         Uses the supplied Section 22 corpus.json envelope. When omitted, default
         corpus lookup remains owned by `agentera usage` and follows
-        `PROFILERA_PROFILE_DIR/intermediate/corpus.json` before platform data-home
+        `AGENTERA_PROFILE_DIR/intermediate/corpus.json` before platform data-home
         defaults.
     project:
       syntax: --project VALUE
@@ -897,14 +900,14 @@ usage_namespace:
   path_contract:
     report_precedence:
       - AGENTERA_USAGE_DIR/USAGE.md
-      - PROFILERA_PROFILE_DIR/USAGE.md
+      - AGENTERA_PROFILE_DIR/USAGE.md
       - platform data home agentera/USAGE.md
     corpus_precedence:
-      - PROFILERA_PROFILE_DIR/intermediate/corpus.json
+      - AGENTERA_PROFILE_DIR/intermediate/corpus.json
       - platform data home agentera/intermediate/corpus.json
     test_isolation: >-
       Facade tests that exercise default text writes must set temporary
-      `AGENTERA_USAGE_DIR` and `PROFILERA_PROFILE_DIR` values and must not write the
+      `AGENTERA_USAGE_DIR` and `AGENTERA_PROFILE_DIR` values and must not write the
       real user data home.
   invalid_input_behavior:
     format_error: >-

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

@@ -2,7 +2,7 @@ schema_version: agentera.app_lifecycle_vocabulary.v1
 status: active_authority
 decision: 54
 purpose: >-
-  Define the app lifecycle vocabulary shared by doctor, hej, upgrade, docs,
+  Define the app lifecycle vocabulary shared by doctor, status, upgrade, docs,
   and tests so structured status metadata, operation verbs, deprecated aliases,
   and consumer ownership boundaries have one machine-readable source.
 sources:
@@ -12,7 +12,7 @@ sources:
     - references/cli/vocabulary.md#app-lifecycle-status-vocabulary
 scope:
   includes:
-    - Agentera app lifecycle status metadata emitted by doctor, hej, and upgrade.
+    - Agentera app lifecycle status metadata emitted by doctor, status, and upgrade.
     - Upgrade workflow operation verbs for app files, data migration, and no-change outcomes.
     - Cross-major status concepts that annotate migration work without adding parallel status enums.
     - Transitional deprecated aliases needed to classify shipped or historical consumers.
@@ -98,19 +98,27 @@ status_concepts:
     definition: >-
       Work that crosses the v2→v3 compatibility boundary (Python managed app-home
       to npm self-contained 3.x). Never implied by stable-channel resolution or
-      @latest; requires explicit --target-major 3 opt-in before apply.
+      @latest while stable tracks 2.x; requires semver forward-major confirmation
+      (running version behind latest on the selected channel) and dry-run preview
+      before --yes apply. Return to the v2 Python line is permanently unsupported
+      after migrating to v3+.
     applies_to_verbs:
       - migrate
       - upgrade
     typical_statuses:
       - manual_review_needed
       - migration_needed
-    requires_explicit_opt_in:
-      flag: --target-major
-      value: 3
+    requires_forward_major_confirmation:
+      mechanism: semver_compare_running_to_latest_on_selected_channel
+      apply_requires:
+        - dry_run_preview
+        - yes_flag
+      authority_cross_ref: references/cli/update-channels.yaml
     item_tag: requires_explicit_major_opt_in
     never_implicit_on_channels:
       - stable
+    irreversible_exit_lines:
+      - v2_python_managed_app_home
     authority_cross_ref: references/cli/update-channels.yaml
 operation_verb_order:
   - install
@@ -147,7 +155,7 @@ operation_verbs:
     lifecycle_allowed: false
 consumer_order:
   - doctor
-  - hej
+  - status
   - upgrade
   - docs
   - tests
@@ -168,7 +176,7 @@ consumers:
       - migrate
       - upgrade
     may_define_new_statuses: false
-  hej:
+  status:
     owns:
       - installed app gate summary exposed in the composite state briefing.
       - recovery prompts derived from doctor and upgrade metadata.

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

@@ -204,9 +204,10 @@ prime_hej_schema_migration_boundary:
   prime_absorbs_hej:
     status: target
     hej_cli: >-
-      Top-level `hej` is removed from the public parser after the alias period.
-      `agentera hej` prints one stderr deprecation naming `prime` and delegates
-      during Phase 1–2.
+      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.
@@ -225,8 +226,9 @@ prime_hej_schema_migration_boundary:
     status: target
     canonical: agentera schema [--format json|yaml]
     alias: >-
-      `agentera describe` prints one stderr deprecation naming `schema` and delegates
-      during Phase 1–2.
+      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.
@@ -260,7 +262,9 @@ plan_routing_distinction:
       is not a CLI command and does not read `.agentera/plan.yaml` by itself.
   state_read:
     invocation: agentera state plan
-    legacy_alias: agentera plan
+    legacy_alias: >-
+      Top-level `agentera plan` was removed on the npm 3.x CLI in Phase 3; use
+      `agentera state plan`.
     surface: CLI routine state read
     meaning: >-
       Read-only access to the active plan artifact summary, tasks, acceptance
@@ -275,8 +279,8 @@ plan_routing_distinction:
       for Planera remains `agentera prime --context planera --format json`.
   agent_guidance: >-
     Use `/agentera plan` when the user wants planning work routed to Planera; use
-    `agentera state plan` (or legacy `agentera plan`) when the agent needs plan
-    artifact state; use `agentera planera` for capability routing guidance; use
+    `agentera state plan` when the agent needs plan artifact state; use
+    `agentera planera` for capability routing guidance; use
     `agentera prime --context planera` for bounded Planera startup context.
 migration_phases:
   phase_1:
@@ -295,15 +299,18 @@ migration_phases:
       - 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.
+        Remove `hej`, public `describe`, and `gate` from top-level parser help
+        and dispatch on the npm 3.x CLI.
       - >-
-        Remove other deprecated top-level parsers except documented capability and
-        lifecycle names and the Phase 1–2 alias set until post-major cleanup.
+        Remove routine-state top-level parsers (`plan`, `progress`, `health`,
+        `todo`, `decisions`, `docs`, `objective`, `experiments`) from help and
+        dispatch on the npm 3.x CLI.
       - >-
-        Deferred final removal of all routine-state top-level aliases after one
-        minor alias release.
+        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
@@ -334,22 +341,29 @@ command_tree_target:
     - report [user]
     - check [maintainer]
 
-deprecated_top_level_aliases:
-  # Command aliases that emit stderr deprecation warnings
-  - { legacy: hej, canonical: prime }
-  - { legacy: describe, canonical: schema }
-  - { legacy: plan, canonical: "state plan" }
-  - { 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" }
+removed_top_level_commands:
+  # Phase 3 on npm 3.x: removed from help and dispatch (unsupported_target)
+  - hej
+  - describe
+  - gate
+  - plan
+  - progress
+  - health
+  - todo
+  - decisions
+  - docs
+  - objective
+  - 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: gate, 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

@@ -14,7 +14,7 @@ scope:
     - Package and distribution metadata that names the suite package shape.
     - Runtime hook packaging prose and metadata for plugin-shipped hooks.
     - Historical references to the removed `bundle-status` command.
-    - Current and legacy references to `skills/agentera/SKILL.md` and v1 skill entry files.
+    - Current references to `skills/agentera/SKILL.md`.
   excludes:
     - Routing and execution vocabulary collapse work.
     - Capability instruction-file rename work.
@@ -32,8 +32,6 @@ canonical_concept_order:
   - removed_bundle_status_command
   - agentera_routing_entry
   - skill_entry_file
-  - v1_skill_entry_file
-  - legacy_hej_bridge
 canonical_concepts:
   agentera_app_files:
     definition: >-
@@ -119,32 +117,6 @@ canonical_concepts:
       - SKILL.md
       - skill file
       - skill entry
-  v1_skill_entry_file:
-    definition: >-
-      A historical standalone v1 skill entry file or path retained in migration
-      notes, tests, stale-path checks, and compatibility fixtures.
-    allowed_terms:
-      - v1 skill entry file
-      - v1 standalone skill entry file
-      - "historical v1 `SKILL.md` file"
-      - v1 skill path
-    forbidden_ambiguous_shortcuts:
-      - SKILL.md
-      - v1 SKILL.md
-      - old skill file
-  legacy_hej_bridge:
-    definition: >-
-      The temporary v1 `/hej` bridge or exact bare `hej` compatibility path that
-      guides users toward `/agentera` and the v2 upgrade path.
-    allowed_terms:
-      - legacy hej bridge
-      - "legacy `/hej` bridge"
-      - v1 hej bridge
-      - "bare `hej` compatibility path"
-    forbidden_ambiguous_shortcuts:
-      - hej skill
-      - legacy skill
-      - old hej
 classification_order:
   - canonical_concept
   - compatibility_identifier
@@ -194,7 +166,7 @@ focused_scan:
     - (retired maintainer measurement tool)
     - skills/agentera/SKILL.md
     - skills/agentera/capabilities/hej/schemas/triggers.yaml
-    - skills/agentera/capabilities/resonera/instructions.md
+    - packages/cli/src/capabilities/resonera/instructions.ts
     - tests/test_cross_capability.py
     - tests/test_resonera_capability.py
     - tests/test_runtime_adapters.py

package/bundle/references/cli/capability-instruction-contract.yaml

@@ -3,9 +3,10 @@ status: active_authority
 decision: 57
 purpose: >-
   Define the Decision 57 capability instruction-file contract: the canonical
-  `instructions.md` file name, implemented CLI/schema first-invocation read
-  discoverability, compact-startup exception boundaries, and runtime behavior
-  that remains intentionally unsupported.
+  `instructions.ts` module path, implemented CLI/schema first-invocation read
+  discoverability, the `prime_context` runtime-enforcement boundary, and
+  retirement of the historical `full`/`compact_startup`/`skip` values
+  superseded by Decision 65.
 sources:
   decision: .agentera/decisions.yaml#decision-57
   prose:
@@ -13,91 +14,87 @@ sources:
     - README.md#development
 scope:
   includes:
-    - Documentation authority for the implemented capability instruction-file name.
+    - Documentation authority for the implemented capability instruction module path.
     - CLI/schema discoverability for first capability invocation startup-read metadata.
-    - Compact-startup exception semantics and boundaries.
-    - Current canonical references to existing `instructions.md` files.
+    - The single `prime_context` first-invocation shape enforced by the runtime.
+    - Current canonical references to existing `instructions.ts` modules.
     - Explicit separation from runtime behavior work.
   excludes:
     - Implementing first-invocation read behavior.
     - Marking Decision 57 satisfied or editing protected vision/objective/profile/installed-app state.
 current_state:
   canonical_instruction_file:
-    path: skills/agentera/capabilities/<name>/instructions.md
+    path: packages/cli/src/capabilities/<name>/instructions.ts
     status: current_canonical_implemented
     definition: >-
-      The human-readable instruction file for each capability.
+      The TypeScript module that exports the capability's behavioral
+      instructions as a default-exported string constant. The runtime loads
+      the compiled .js path and serves the prose through the slim
+      `capability_context` capsule's `prose` field.
   legacy_instruction_file:
+    path: skills/agentera/capabilities/<name>/instructions.md
+    status: historical_or_compatibility_evidence_only
+    definition: >-
+      The pre-D65 Markdown instruction filename. It may survive only in
+      archived history, compatibility fixtures, benchmark evidence, or
+      explicit migration documentation; real capability directories do not
+      use it as canonical.
+  legacy_prose_file:
     path: skills/agentera/capabilities/<name>/prose.md
     status: historical_or_compatibility_evidence_only
     definition: >-
-      The former capability instruction filename. It may survive only in archived
-      history, compatibility fixtures, benchmark evidence, or explicit migration
-      documentation; real capability directories do not use it as canonical.
+      The pre-D57 capability instruction filename. It may survive only in
+      archived history, compatibility fixtures, benchmark evidence, or
+      explicit migration documentation; real capability directories do not
+      use it as canonical.
   validator_requirement:
-    current_required_path: instructions.md
-    future_required_path: instructions.md
+    current_required_path: packages/cli/src/capabilities/<name>/instructions.ts
+    future_required_path: packages/cli/src/capabilities/<name>/instructions.ts
     status: current_requirement_enforced
   cli_metadata:
     field: first_invocation_read
     status: emitted_in_prime_capability_context
     current_behavior: >-
       `agentera prime --context <name> --format json` emits
-      `capability_context` metadata including `first_invocation_read` for
-      supported capabilities. Historical `hej --capability-context` is removed in 3.0.
+      `capability_context` metadata including `first_invocation_read`
+      (value: `prime_context`, runtime_enforcement: true) and the full prose
+      in the `prose` field for supported capabilities. Historical
+      `hej --capability-context` is removed in 3.0.
 first_invocation_read:
-  field_status: cli_schema_discoverability_implemented
+  field_status: runtime_enforced
   definition: >-
-    Capability metadata declaring what instruction content an agent must read on
-    the first invocation of that capability in a session.
+    Capability metadata declaring what instruction content an agent must
+    read on the first invocation of that capability in a session. Decision
+    65 collapses the legacy `full`/`compact_startup` distinction into a
+    single `prime_context` value because the CLI now owns the prose and
+    the runtime can mechanically shell out to the prime command.
   allowed_values:
-    full:
-      meaning: >-
-        The first capability invocation must read `instructions.md` in full before
-        executing capability-specific work.
-      obligation: full_instruction_file_read_required
-    compact_startup:
-      meaning: >-
-        A declared compact startup contract may satisfy initial orientation without
-        reading the full instruction file first.
-      obligation: compact_contract_must_name_covered_guidance_and_escalation_rules
-    skip:
+    prime_context:
       meaning: >-
-        No first-invocation instruction read is required for the declared scope.
-      obligation: requires_explicit_contract_justification
-      caution: >-
-        Reserved for narrow future surfaces; not a default and not implemented by
-        this authority.
-  default_rule: full
+        The first capability invocation must shell out to
+        `agentera prime --context <name> --format json` and read the
+        returned `prose` field (the full Markdown body) before executing
+        capability-specific work.
+      obligation: shell out to agentera prime --context <name> --format json
+  default_rule: prime_context
   full_read_obligation: >-
-    On initial capability invocation, read `instructions.md` in full unless that
-    capability declares a compact-startup exception with explicit coverage and
-    escalation boundaries.
-compact_startup_exception:
-  status: implemented_for_planera_compact_startup_discoverability
-  allowed_when:
-    - A machine-readable startup contract is available through supported state access.
-    - The compact contract states which instruction topics it covers.
-    - The compact contract states when the agent must escalate to a full instruction-file read.
-    - The compact contract preserves unsupported-command and raw-artifact-read boundaries.
-  not_allowed_when:
-    - The agent is editing the capability's own instructions or schemas.
-    - The compact contract is missing, incomplete, stale, or contradictory.
-    - The requested work touches behavior not covered by the compact contract.
-    - Safety rails, validation, exit semantics, or cross-capability boundaries are ambiguous.
+    On initial capability invocation, shell out to
+    `agentera prime --context <name> --format json` and read the
+    `capability_context.prose` field in full.
 implementation_state:
-  instructions_md_files: renamed
-  validators_require_instructions_md: true
+  instructions_ts_modules: implemented
+  validators_require_instructions_ts: true
   first_invocation_read_cli_metadata: true
   first_invocation_read_schema_metadata: true
-  runtime_first_invocation_behavior: false
-  descriptors_rewritten_to_instructions_md: true
-  package_metadata_rewritten_to_instructions_md: true
+  runtime_first_invocation_behavior: true
+  descriptors_rewritten_to_prime_command: true
+  package_metadata_rewritten_to_prime_command: true
 compatibility_preservation:
   preserve_legacy_references_only_when_classified:
-    - skills/agentera/capabilities/*/instructions.md paths
+    - skills/agentera/capabilities/*/instructions.md paths (historical)
+    - packages/cli/src/capabilities/*/instructions.ts paths (current canonical)
     - skills/agentera/capability_schema_contract.yaml directory requirements
-    - runtime descriptors and generated agent guidance that point to `instructions.md`
+    - runtime descriptors and generated agent guidance that point to `instructions.md` (retired)
     - archived v1/v2 migration records and progress evidence
     - compatibility fixtures and tests that intentionally preserve old behavior evidence
     - README, AGENTS, and vocabulary references that explicitly describe the current canonical state
@@ -116,6 +113,50 @@ surface_inventory:
   capability_schema_contract: current_canonical_validator_reference
   runtime_descriptors: current_canonical_instructions_md_pointers
   capability_instruction_files: current_canonical_instruction_files
+evaluator_handoff:
+  status: implemented
+  purpose: >-
+    Define the inspektera evaluation report schema and citation requirements
+    for orkestrera Step 3 Surface 2 delegations and post-plan health checks.
+  report_schema_version: agentera.inspekteraEvaluationReport.v1
+  row_schema:
+    required_fields:
+      - criterion
+      - status
+      - evidence
+    status_values:
+      - PASS
+      - WARN
+      - FAIL
+    citation_required_for:
+      - WARN
+      - FAIL
+    citation_formats:
+      file_line:
+        pattern: "^[^:\\s]+:\\d+$"
+        description: Relative repo path with 1-based line number, e.g. TODO.md:15
+      not_applicable:
+        prefix: "not-applicable:"
+        min_reason_length: 8
+        description: >-
+          Use when no file anchor exists; prefix with not-applicable: and give a
+          concrete reason (at least 8 characters after the prefix).
+    warn_verify_command:
+      required_when: file_line_citation
+      allowed_prefixes:
+        - grep
+        - git show
+      description: >-
+        WARN rows with a file:line citation MUST include verify_command with the
+        exact grep or git show invocation that reproduces the evidence at the
+        cited line.
+  orchestration_context_fields:
+    output_requirements:
+      citation_required_for:
+        - WARN
+        - FAIL
+      warn_verify_command_required: true
+      schema_authority: references/cli/capability-instruction-contract.yaml#evaluator_handoff
 docs_delegation:
   document: references/cli/vocabulary.md
   required_anchor: Capability instruction contract