agentera 3.0.0-dev.5 → 3.0.0-dev.7

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

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

@@ -7,47 +7,47 @@ classification:
   mutation_capable:
     description: Needs file write, edit, and/or shell execution to fulfill purpose
     capabilities:
-      realisera:
+      build:
         permission: {write: allow, bash: allow}
         rationale: Autonomous dev execution — writes code, runs tests/builds, commits
-      optimera:
+      optimize:
         permission: {write: allow, bash: allow}
         rationale: Metric-driven optimization — runs experiments, writes harnesses
-      orkestrera:
+      orchestrate:
         permission: {write: allow, bash: allow}
         rationale: Multi-cycle orchestration — dispatches workers, updates plan/progress
-      dokumentera:
+      document:
         permission: {write: allow, bash: deny}
         rationale: Documentation generation — creates/updates doc files
-      planera:
+      plan:
         permission: {write: allow, bash: deny}
         rationale: Plan management — writes plan.yaml, archives completed plans
 
   contextual_write:
     description: Writes owned Agentera state artifacts
     capabilities:
-      visionera:
+      vision:
         permission: {write: allow, bash: deny}
         rationale: Writes vision.yaml, archives old visions
-      resonera:
+      discuss:
         permission: {write: allow, bash: deny}
         rationale: Writes decisions.yaml, may update TODO.md
-      visualisera:
+      design:
         permission: {write: allow, bash: deny}
         rationale: Writes DESIGN.md, archives old designs
-      profilera:
+      profile:
         permission: {write: allow, bash: allow}
         rationale: Runs extraction scripts, writes PROFILE.md
-      inspektera:
+      audit:
         permission: {write: allow, bash: deny}
         rationale: Writes health.yaml audit reports
 
   read_only:
     description: Only reads files, searches, analyzes
     capabilities:
-      hej:
+      status:
         permission: {write: deny, bash: deny}
         rationale: Strictly read-only orientation dashboard
-      inspirera:
+      research:
         permission: {write: deny, bash: deny}
         rationale: Analysis-only creative exploration

package/bundle/references/cli/coexistence-probe.yaml

@@ -0,0 +1,13 @@
+# v2/v3 coexistence doctor warning contract (both CLI lines).
+schema_version: agentera.coexistenceProbe.v1
+section_header: Coexistence
+warning:
+  headline: "v3 detected alongside v2; pick one line"
+  resolutions:
+    - complete v3 migration
+    - uninstall v3
+    - stay on v2 explicitly
+naming_divergence:
+  description: "v3 uses English capability IDs (status, vision, discuss, research, plan, build, optimize, audit, document, profile, design, orchestrate); v2 stable uses Swedish -era IDs (hej, visionera, resonera, inspirera, planera, realisera, optimera, inspektera, dokumentera, profilera, visualisera, orkestrera)"
+  v3_canonical: [status, vision, discuss, research, plan, build, optimize, audit, document, profile, design, orchestrate]
+  v2_stable: [hej, visionera, resonera, inspirera, planera, realisera, optimera, inspektera, dokumentera, profilera, visualisera, orkestrera]

package/bundle/references/cli/parity-expected-actual-template.md

@@ -0,0 +1,30 @@
+# Parity EXPECTED/ACTUAL bug-demonstration template
+
+Apply this pattern to `npmParityMatrix` / Python-oracle parity rows when fixing a
+regression: land a **demonstrate** commit first, then a **fix** commit that only
+flips the assertion.
+
+## Workflow
+
+1. **Demonstrate commit** — test passes on broken behavior; correct expectation
+   preserved in a block comment (`EXPECTED`); wrong behavior asserted (`ACTUAL`).
+2. **Fix commit** — delete comment markers and `ACTUAL` line; `EXPECTED` becomes the
+   live assertion. No other edits in the fix commit.
+
+## Minimal vitest shape
+
+See `packages/cli/test/cli/parityExpectedActualTemplate.test.ts` for a runnable
+micro-example. For real parity rows, mirror the pattern in the oracle fixture row
+and `npmParityMatrix.test.ts` drift assertions.
+
+## npmParityMatrix row
+
+When adding a row to the parity matrix for a pre-existing bug:
+
+- Register the row with `drift_direction: equal` as the target after fix.
+- In the demonstrate pass, temporarily pin oracle shape to the **wrong** envelope
+  or assert `ACTUAL` substring in a dedicated regression test.
+- Fix pass restores `equal` against the corrected CLI output.
+
+Do not apply EXPECTED/ACTUAL by default to every row — only where bisect clarity
+justifies the two-commit ritual.

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

@@ -31,7 +31,7 @@ compatibility_boundary: >-
 canonical_concept_order:
   - request_to_capability_routing
   - next_action_recommendation
-  - orkestrera_task_assignment
+  - orchestrate_task_assignment
   - worker_launch
   - runtime_subagent_support
   - worker_safety_git_commit
@@ -40,7 +40,7 @@ canonical_concepts:
     definition: >-
       Agentera chooses the capability that should handle a user request, using
       direct routes, primary route aliases, trigger schemas, disambiguation, or
-      fallback to hej.
+      fallback to status.
     preferred_terms:
       - Agentera router
       - request-to-capability routing
@@ -65,15 +65,15 @@ canonical_concepts:
       - force
       - chain
       - conductor handoff
-  orkestrera_task_assignment:
+  orchestrate_task_assignment:
     definition: >-
-      Orkestrera assigns approved plan work to a worker capability during an
+      Orchestrate assigns approved plan work to a worker capability during an
       explicitly orchestrated flow; it evaluates the result instead of implementing
       the task itself.
     preferred_terms:
       - delegate
       - delegation
-      - Orkestrera task delegation
+      - Orchestrate task delegation
       - assigned plan work
     forbidden_ambiguous_shortcuts:
       - conductor
@@ -82,7 +82,7 @@ canonical_concepts:
       - orchestrator implementation
   worker_launch:
     definition: >-
-      Realisera or Optimera starts a worker through the host runtime when an
+      Build or Optimize starts a worker through the host runtime when an
       implementation or measurement cycle needs isolated execution.
     preferred_terms:
       - spawn

package/bundle/references/cli/routing-model.md

@@ -0,0 +1,96 @@
+# Five-layer routing model
+
+Origin: Decision 76 (2026-06-30) — LLM-primary routing model. Retires the
+deterministic NL routing engine and repositions the trigger schema as
+LLM-readable intent documentation. Builds on the original five-layer concept
+from Decision 42 (2026-05-04), redefining Layers 3-4 as LLM-native.
+
+The Agentera routing model resolves incoming requests to a capability across
+five layers. Layers 1, 2, and 5 are deterministic dispatch (bare invocation,
+exact alias, no match); they are implemented and unchanged. Layers 3 and 4
+cover natural-language requests. Per Decision 76, the LLM host — the AI model
+that receives the user's message — owns natural-language routing natively. The
+trigger schema (`description`, `disambiguates_against`, `priority`, phase
+context) provides LLM-readable intent documentation the host consults; there is
+no scoring engine, no confidence threshold, and no borderline band. Layer 4
+(formerly borderline-band disambiguation) is dissolved into Layer 3: the LLM
+resolves ambiguity natively, using `disambiguates_against` hints as advisory
+context. Decision 75's request-vs-state mutual exclusivity is dissolved: request
+intent and state-readiness are both advisory context the LLM consults.
+
+## Layer 1: Bare `/agentera` or bare `hej` — delegate to prime
+
+- **Input pattern**: the request is `/agentera` with no additional text, or the
+  complete user message is exactly `hej`.
+- **Action**: delegate immediately to the status capability. Status performs
+  state-aware routing through the `agentera prime` composite result, which
+  condenses project artifacts and suggests the most useful next capability.
+  This is deterministic and never wrong. Bare `hej` must not be handled as a
+  generic greeting.
+- **Implementation status**: implemented and unchanged.
+
+## Layer 2: capability name or `/agentera <primary-alias>` — direct route
+
+- **Input pattern**: the request text exactly matches a capability name
+  (case-insensitive), or exactly matches one primary alias from
+  `capability_schema_contract.yaml` `ROUTE_ALIASES.primary_aliases`, or begins
+  with a canonical capability name followed by more text (`/agentera <capability>
+  <topic>`).
+- **Action**: route directly to that capability without evaluating natural-language
+  trigger descriptions. Pass any remaining text as the user's topic or instruction.
+  Each capability has exactly one primary alias; secondary wording stays in
+  capability trigger schemas below this layer.
+- **Implementation status**: implemented and unchanged.
+
+## Layer 3: Natural language — LLM-native routing
+
+- **Input pattern**: the request is natural language (e.g. "help me think
+  through this") that does not match Layer 1 or Layer 2.
+- **Action**: the LLM host routes natively. It consults the trigger schema's
+  `description` fields (what each capability does), `disambiguates_against`
+  hints (how to tell near-equal capabilities apart), and `priority`
+  (relevance precedence) as LLM-readable intent documentation, then selects a
+  capability. There are no confidence scores, no thresholds, and no
+  weighted-average computation; the LLM reads the intent descriptions and
+  routes.
+- **Resolving ambiguity**: when two capabilities could match a request, the
+  LLM host resolves the ambiguity natively, surfacing the
+  `disambiguates_against.hint` strings as advisory context when it asks the
+  user to confirm or clarify. The hints supply the words; the LLM supplies the
+  judgment.
+- **Implementation status**: implemented — the LLM host owns this layer.
+  `references/cli/trigger-schema-enrichment.md` is the intent documentation
+  contract the host reads.
+
+## Layer 4: Dissolved into Layer 3
+
+Layer 4 formerly described a borderline-band disambiguation engine that fired
+when two capabilities scored within a configurable band. Decision 76 retired
+that engine: ambiguity resolution is now part of Layer 3, performed natively by
+the LLM host using the `disambiguates_against` hints as advisory context. There
+is no separate disambiguation layer, no borderline band, and no
+disambiguation-engine output schema.
+
+## Layer 5: No match — fallback to status
+
+- **Input pattern**: the LLM host cannot map the request to any capability from
+  the trigger schema's intent descriptions.
+- **Action**: route to status for orientation. Status handles greetings, status
+  requests, and ambiguous inputs.
+- **Implementation status**: implemented and unchanged.
+
+## Ownership boundaries
+
+- **This document** defines what Layers 1-5 mean: their input patterns, actions,
+  and implementation status.
+- **`skills/agentera/capability_schema_contract.yaml`** (`ENTRY_SCHEMA.fields.priority`
+  and `FIELD_RULES.TRIGGERS.priority`) defines trigger `priority` values
+  (`high`, `medium`, `low`) as an advisory relevance-precedence hint the LLM host
+  reads — not a scoring weight.
+- **Per-capability `schemas/triggers.yaml`** owns the trigger `description`,
+  `priority`, and `disambiguates_against` intent documentation that the LLM host
+  consults for Layer 3 routing. `references/cli/trigger-schema-enrichment.md` is
+  the intent documentation contract; pattern matching and scoring belong to
+  neither, having been retired by Decision 76.
+- **`skills/agentera/SKILL.md`** is the thin bootstrap routing surface per Decision
+  74; it cross-references this document rather than restating the full model.

package/bundle/references/cli/single-name-protocol.yaml

@@ -0,0 +1,42 @@
+schema_version: agentera.single_name_protocol.v1
+status: active_authority
+decision: 58
+purpose: >-
+  Machine-readable Decision 58 boundary: forbidden legacy protocol identifiers
+  and scan surfaces for the single-name protocol regression test.
+human_index:
+  document: references/cli/vocabulary.md
+forbidden_protocol_substrings:
+  - pattern: instruction_file
+    rationale: D65 renamed DIRECTORY_REQUIREMENTS and contract fields to instruction_module.
+  - pattern: canonical_instruction_file
+    rationale: Use canonical_instruction_module in capability-instruction-contract.yaml.
+  - pattern: legacy_instruction_file
+    rationale: Historical paths belong in archive or migration modules only.
+  - pattern: instructionPath
+    rationale: capabilityContract loader exposes instructionModulePath only.
+forbidden_storage_protocol_markdown_artifacts:
+  - PROGRESS.md
+  - PLAN.md
+  - DECISIONS.md
+  - VISION.md
+  - HEALTH.md
+  - DOCS.md
+  - OBJECTIVE.md
+  - EXPERIMENTS.md
+scan_roots:
+  - packages/cli/src
+  - skills/agentera/capability_schema_contract.yaml
+  - skills/agentera/protocol.yaml
+  - references/cli/capability-instruction-contract.yaml
+  - references/cli/vocabulary.md
+  - references/cli/vocabulary-index.yaml
+  - registry.json
+scan_exclude_globs:
+  - "**/capabilities/**/instructions.ts"
+  - "**/migrateArtifactsV1ToV2.ts"
+  - "**/migrateArtifactsV2ToV3.ts"
+  - "**/migrateArtifacts*.ts"
+  - "**/*.test.ts"
+  - "**/test/**"
+comment_line_exempt: true

package/bundle/references/cli/trigger-schema-enrichment.md

@@ -0,0 +1,136 @@
+# Trigger intent documentation contract
+
+Authority for Layer 3 LLM-native capability routing. This document defines the
+trigger-schema fields the LLM host consults to understand what each capability
+does and how to disambiguate near-equal requests. The fields are documentation
+the host reads, not inputs to a scoring engine.
+
+- **Authority path:** `references/cli/trigger-schema-enrichment.md`
+- **Schema contract:** `skills/agentera/capability_schema_contract.yaml` (the
+  contract loader at `packages/cli/src/registries/capabilityContract.ts` consumes it)
+- **Trigger files:** `skills/agentera/capabilities/<name>/schemas/triggers.yaml`
+- **Scope:** Layer 3 (LLM-native natural-language routing) of the five-layer
+  routing model. Layer 4 (formerly borderline-band disambiguation) is dissolved
+  into Layer 3. Layers 1, 2, and 5 are unchanged.
+
+## Decision 76 — repositioning
+
+Decision 76 (2026-06-30) retires the deterministic NL routing engine. The LLM
+host — the AI model that receives the user's message — owns natural-language
+routing natively. This document is repositioned from a scoring-enrichment
+contract to the **trigger intent documentation contract**: it defines the
+`triggers.yaml` fields that help the LLM host understand what each capability
+does and how to disambiguate near-equal requests.
+
+The fields stay as documentation, not as scoring inputs. The LLM host reads the
+descriptions and disambiguates natively; `priority` and `disambiguates_against`
+are advisory hints, not scoring weights. There is no scoring algorithm, no
+confidence threshold, no borderline band, and no `prime --route` output schema.
+Decision 75's request-vs-state mutual exclusivity is dissolved: request intent
+and state-readiness are both advisory context the LLM consults. Decision 76
+supersedes Decision 75 design choices 2 (request-derived scoring as router), 4
+(mutual exclusivity), and 5 (pure request-derived).
+
+Decision 76 records the design choices and rejected alternatives (including the
+tuning-the-engine and reposition-`--route` alternatives that were rejected).
+
+## 1. Field shape
+
+The fields below are the LLM-readable intent documentation the host consults.
+`description` and `priority` are base trigger fields required on every
+`TRIGGERS` entry; `disambiguates_against` is an optional enrichment that gives
+the host disambiguation words to surface when a request could match more than
+one capability.
+
+### 1.1 `description`
+
+- **Type:** non-empty string (required on every `TRIGGERS` entry).
+- **Meaning:** the LLM-readable explanation of what this trigger entry routes to.
+  The LLM host reads this to decide whether a natural-language request matches
+  the capability's intent. Prose that names the capability's purpose and the
+  request shapes it owns reads better than keyword lists; write it for a reader
+  who has never seen the capability before.
+- **Validation failure:** a missing, empty, or non-string `description` fails
+  validation with an error message naming the offending entry ID.
+
+```
+TRIGGERS:
+  1:
+    id: T2
+    description: >-
+      Audit and codebase health requests.
+    priority: medium
+    patterns:
+      - "check code health"
+      - "architecture review"
+```
+
+### 1.2 `disambiguates_against`
+
+- **Type:** list of mappings. Each entry MUST contain:
+  - `capability` — string referencing a valid capability ID (one of the twelve
+    English canonical IDs enumerated by `ROUTE_ALIASES.primary_aliases` in
+    `capability_schema_contract.yaml`: `status`, `vision`, `discuss`, `research`,
+    `plan`, `build`, `optimize`, `audit`, `document`, `profile`, `design`,
+    `orchestrate`).
+  - `hint` — non-empty string distinguishing this trigger's intent from the
+    named capability on near-equal requests.
+- **Meaning:** declares which other capabilities this trigger's intent could be
+  confused with, with a hint the LLM host consults when it sees a request that
+  could match more than one capability. The list is advisory: the LLM host
+  resolves ambiguity natively and MAY surface the hint when asking the user to
+  confirm or clarify. The hint supplies the words; the LLM supplies the
+  judgment.
+- **Validation failure:** a `capability` value that is not one of the twelve
+  canonical IDs, a missing `hint`, an empty `hint`, or an entry that is not a
+  mapping fails validation with the offending entry ID and the constraint.
+
+```
+disambiguates_against:
+  - capability: build
+    hint: "vision refines existing project direction; build implements code"
+  - capability: optimize
+    hint: "vision is about what to build, not tuning existing code"
+```
+
+### 1.3 `priority`
+
+- **Type:** string enum `high` | `medium` | `low` (required on every `TRIGGERS`
+  entry).
+- **Meaning:** advisory relevance-precedence hint the LLM host reads alongside
+  `description` when deciding which capability best fits a request. `high`
+  marks a capability that owns the request strongly; `low` marks a capability
+  that is a plausible but weaker fit. It is not a scoring weight and feeds no
+  weighted-average calculation; the LLM host uses it as one signal among the
+  intent documentation.
+- **Validation failure:** a missing `priority` or a value outside `high`,
+  `medium`, `low` fails validation with the offending entry ID.
+
+```
+priority: high
+```
+
+## 2. Defaults summary
+
+| Field | Required | Default when absent |
+| --- | --- | --- |
+| `description` | required | — |
+| `disambiguates_against` | optional | empty list (no explicit collisions declared) |
+| `priority` | required (`TRIGGERS`) | — |
+
+`description` and `priority` are required on every `TRIGGERS` entry and have no
+default. `disambiguates_against` is optional and defaults to an empty list. The
+loader at `packages/cli/src/registries/capabilityContract.ts` is the consumer of
+these shapes; tests and source that need them read through the loader rather than
+re-declaring the values (per the AGENTS.md rule against duplicating
+contract-owned values).
+
+## 3. Acceptance criteria mapping
+
+| Criterion | Section |
+| --- | --- |
+| `description` is a non-empty string on every `TRIGGERS` entry | §1.1 |
+| `disambiguates_against` entries reference a valid capability ID and include a non-empty hint | §1.2 |
+| `priority` is one of `high` / `medium` / `low` on every `TRIGGERS` entry | §1.3 |
+| Document reframed as LLM-readable intent documentation; no scoring algorithm, thresholds, borderline band, or `--route` output schema | Decision 76, §1 |
+| Decision artifact lists each choice, ≥1 alternative, and rationale | Decision 76 in `.agentera/decisions.yaml` |

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

@@ -37,6 +37,7 @@ channels:
       concept: forward_successor_line
       channel: development
       version: "3.0.0"
+      announced: true
       npm:
         dist_tag: next
       npm_only_advisory: >-
@@ -63,6 +64,21 @@ channels:
       feat/v3 branch and v3 CLI are npm-only; v2→v3 is a one-way upgrade through
       npx @next, not through uvx or git checkout installs.
     distribution_major: 3
+    next_major:
+      concept: forward_successor_line
+      channel: development
+      version: "3.0.0"
+      announced: true
+      npm:
+        dist_tag: next
+      npm_only_advisory: >-
+        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
+      irreversible_advisory: >-
+        Forward migration to the v3 line is one-way; return to the prior
+        Python support line is permanently unsupported.
     resolution:
       npm:
         dist_tag: next