agentera 3.0.0-dev.3 → 3.0.0-dev.31

package/bundle/references/artifacts/verbosity-budget-authority.yaml

@@ -0,0 +1,42 @@
+schema_version: agentera.verbosityBudgetAuthority.v1
+status: active_authority
+purpose: >-
+  Define which artifact schema owns each verbosity budget. Budget values stay
+  in the owning schema so validators and future consumers cannot introduce a
+  second value table.
+authority:
+  source: references/artifacts/verbosity-budget-authority.yaml
+  schema_directory: ../../skills/agentera/schemas/artifacts
+  single_source_rule: >-
+    Each supported artifact resolves to exactly one schema BUDGET group.
+    Missing, unreadable, duplicate, or malformed declarations are authority
+    errors; consumers must not substitute generic or historical limits.
+classification:
+  numeric_limit: A positive max_words value.
+  explicit_no_limit: A null max_words value.
+  non_word_unit: A positive token_budget value; it does not authorize word lint.
+  invalid_declaration: A missing, duplicate, ambiguous, or malformed declaration.
+scope:
+  supported_artifacts:
+    - artifact_id: changelog
+      schema: changelog.yaml
+    - artifact_id: decisions
+      schema: decisions.yaml
+    - artifact_id: design
+      schema: design.yaml
+    - artifact_id: docs
+      schema: docs.yaml
+    - artifact_id: experiments
+      schema: experiments.yaml
+    - artifact_id: health
+      schema: health.yaml
+    - artifact_id: objective
+      schema: objective.yaml
+    - artifact_id: plan
+      schema: plan.yaml
+    - artifact_id: progress
+      schema: progress.yaml
+    - artifact_id: todo
+      schema: todo.yaml
+    - artifact_id: vision
+      schema: vision.yaml

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

@@ -62,7 +62,7 @@ slash_route_aliases:
     Decision 43 aliases are exact `/agentera <alias>` routes, not CLI state
     commands. Teaching `status`, `build`, `audit`, or `document` as CLI commands
     would blur route vocabulary with state access; the shared word `plan` keeps
-    separate meanings as `/agentera plan` routing and `agentera plan` state.
+     separate meanings as `/agentera plan` routing and `agentera state plan` state.
 doctor:
   status: implemented_hard_rename
   command: doctor
@@ -70,23 +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:
-    project_artifact_health: agentera health
     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 Agentera CLI/install/runtime
-    self-check vocabulary only; artifact health and codebase audits remain owned
-    by `agentera health` and inspektera.
+     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
@@ -172,7 +170,7 @@ structured_output:
             - summary_fields
             - entry_fields
           complete_semantics: >-
-            When `complete_for_plan_artifact` is true, `agentera plan --format
+            When `complete_for_plan_artifact` is true, `agentera state plan --format
             json` includes plan summary metadata, tasks, dependencies, acceptance
             criteria, evidence, overall acceptance, surprises, and previous-plan
             archive references needed for normal read-only startup/evaluation
@@ -224,18 +222,22 @@ structured_output:
       fields:
         - command
         - status
-        - bundle
+        - app_home
+        - app
         - mode
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
         - objective
         - state_presence
+        - project_integration
         - attention
+        - history
+        - shared_skill
         - decision_attention
         - next_action
         - orchestration_context
@@ -282,10 +284,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,
@@ -328,8 +330,9 @@ structured_output:
             `agentera prime --format json` may include one bounded `decision_attention`
             payload when returned decisions require satisfaction review. The payload
             derives from the same `_decision_context_entry` and
-            `_decision_satisfaction_context` semantics as `agentera decisions --format
-            json`, never infers satisfaction, never mutates `.agentera/decisions.yaml`,
+             `_decision_satisfaction_context` semantics as bounded `agentera state
+             decisions list --limit 20 --format json` plus exact `state decisions
+             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
@@ -360,9 +363,7 @@ startup_completeness:
     before any raw artifact read. Complete startup state must never require raw
     artifact reads for normal capability startup.
   current_cli_fallback:
-    - agentera plan --format json
-    - agentera docs --format json
-    - agentera progress --format json
+     - agentera state plan --format json
   state_families_added:
     - plan task details, dependencies, acceptance criteria, and evidence summaries
     - docs artifact mapping and source-contract completeness metadata
@@ -405,11 +406,11 @@ evidence_context_target_contract:
           - vision
           - profile
         fallback_commands:
-          - agentera decisions --format json
+          - agentera state decisions list --limit 20 --format json
         caveats:
           - profile-derived state is stale and must not trigger profile refresh
           - orchestration_context is incomplete for missing decisions, vision, and profile state
-      - command: agentera plan --format json
+      - command: agentera state plan --format json
         included_state:
           - active plan header and summary
           - task dependencies
@@ -419,15 +420,7 @@ evidence_context_target_contract:
           - previous_plan_archived pointer
         missing_state: []
         raw_artifact_reads_required: false
-      - command: agentera progress --format json
-        included_state:
-          - latest progress cycles
-          - latest verification text
-          - cycle provenance
-        missing_state:
-          - explicit retry-attempt count
-        raw_artifact_reads_required: false
-      - command: agentera docs --format json
+      - command: agentera state docs --format json
         included_state:
           - artifact mapping
           - version files
@@ -435,37 +428,20 @@ evidence_context_target_contract:
           - indexed document freshness
         missing_state: []
         raw_artifact_reads_required: false
-      - command: agentera health --format json
-        included_state:
-          - latest audit
-          - dimension grades
-          - findings
-          - trajectory
-        missing_state: []
-        raw_artifact_reads_required: false
-      - command: agentera todo --format json
+      - command: agentera state todo --format json
         included_state:
           - open 2.3.10 evidence-context TODO
           - deferred 2.3.11 and 2.3.12 source-contract TODOs
           - known open issues
         missing_state: []
         raw_artifact_reads_required: false
-      - command: agentera decisions --format json
-        included_state:
-          - decisions 51 and 52 with complete context
-          - compacted historical decision summaries
-        missing_state:
-          - full context for 40 compacted historical entries
-        raw_artifact_reads_required: false
-        caveats:
-          - compacted decisions expose missing_fields and caveats instead of reconstructed history
     last_resort_raw_fallbacks:
       - reason: archived previous-plan status is not exposed by routine CLI state
         path: .agentera/archive/PLAN-2026-05-15-2-3-9-dokumentera-closeout-context-source-contract.yaml
         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
@@ -509,28 +485,28 @@ evidence_context_target_contract:
     required_for_normal_task_evaluation:
       - family: evaluation_target
         source: plan/orchestration CLI state
-        fallback: agentera plan --format json
+        fallback: agentera state plan --format json
       - family: plan_criteria
-        source: agentera plan --format json entries.acceptance
+        source: agentera state plan --format json entries.acceptance
         fallback: none when complete_for_plan_artifact is true
       - family: progress_verification
-        source: agentera progress --format json latest verification
-        fallback: agentera progress --format json
+        source: agentera state progress list --limit 20 --format json latest verification
+        fallback: agentera state progress get --id ID --format json
       - family: docs_state
-        source: agentera docs --format json summary and entries
-        fallback: agentera docs --format json
+        source: agentera state docs --format json summary and entries
+        fallback: agentera state docs --format json
       - family: health_state
-        source: agentera health --format json latest audit
-        fallback: agentera health --format json
+        source: agentera state health list --limit 20 --format json latest audit
+        fallback: agentera state health get --id ID --format json
       - family: todo_state
-        source: agentera todo --format json known issues and source-contract TODOs
-        fallback: agentera todo --format json
+        source: agentera state todo --format json known issues and source-contract TODOs
+        fallback: agentera state todo --format json
       - family: source_contract
         source: evidence_context.source_contract
         fallback: listed existing CLI commands before raw reads
     optional_or_caveated_for_normal_task_evaluation:
       - family: decisions_context
-        source: agentera decisions --format json
+        source: agentera state decisions list --limit 20 --format json
         caveat: compacted historical entries remain incomplete and must not be reconstructed from raw artifacts
       - family: vision_context
         source: hej startup only when included by capability context
@@ -584,18 +560,22 @@ field_selection:
       fields:
         - command
         - status
-        - bundle
+        - app_home
+        - app
         - mode
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
         - objective
         - state_presence
+        - project_integration
         - attention
+        - history
+        - shared_skill
         - decision_attention
         - next_action
         - orchestration_context
@@ -755,11 +735,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 +792,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 +815,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 +860,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 +880,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.
@@ -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
@@ -155,7 +154,7 @@ operation_verbs:
     lifecycle_allowed: false
 consumer_order:
   - doctor
-  - hej
+  - status
   - upgrade
   - docs
   - tests
@@ -176,7 +175,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

@@ -174,7 +174,7 @@ audience_namespaces:
       validate:
         canonical_shape: agentera check validate <family> [target options]
         delegates_from: validate
-        notes: Preserves existing validate families (capability, artifact, descriptors, etc.).
+        notes: Preserves current validate families including capability and artifact validation.
       verify:
         canonical_shape: agentera check verify <family> <target> [options]
         delegates_from: verify
@@ -186,16 +186,17 @@ audience_namespaces:
         canonical_shape: agentera check compact [--project PATH] [--mode check|fix] [--format text|json]
         delegates_from:
           - compact
-          - gate
         notes: >-
-          `check compact` in default check-only mode matches today's `agentera gate`.
-          Artifact compaction budget checks remain on `check compact`.
-    legacy_top_level_aliases:
-      - validate
+          `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
-      - gate
-      - compact
+      - validate
 help_grouping:
   agent: [prime, state, schema, capabilities]
   user: [upgrade, doctor, report]
@@ -204,9 +205,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 +227,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,24 +263,26 @@ 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` is capability routing, not a state-read alias;
+      use `agentera state plan` 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 planera
+    invocation: agentera plan
     surface: CLI top-level capability routing command
     meaning: >-
-      Emits Planera routing guidance prose/schemas pointers. Does not replace
+      Emits plan capability routing guidance prose/schemas pointers. Does not replace
       `state plan` reads or `/agentera plan` slash routing. Capability startup JSON
-      for Planera remains `agentera prime --context planera --format 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` (or legacy `agentera 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.
+    `agentera state plan` 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
@@ -295,15 +300,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,11 +342,26 @@ command_tree_target:
     - report [user]
     - check [maintainer]
 
-deprecated_top_level_aliases:
-  # Command aliases that emit stderr deprecation warnings
+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: plan, canonical: "state plan" }
+  - { legacy: gate, canonical: "check compact" }
   - { legacy: progress, canonical: "state progress" }
   - { legacy: health, canonical: "state health" }
   - { legacy: todo, canonical: "state todo" }
@@ -346,10 +369,16 @@ deprecated_top_level_aliases:
   - { 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: 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: []