agentera 3.0.0-dev.6 → 3.0.0-dev.7

package/bundle/extract-corpus-parity.json

@@ -0,0 +1,23 @@
+{
+  "schema_version": "agentera-extract-corpus-parity-v1",
+  "adapter_version": "agentera-v2-corpus-1",
+  "max_sqlite_sessions": 60,
+  "max_sqlite_rows": 100000,
+  "max_tool_arg_text": 500,
+  "copilot_sparse_remediation": "/chronicle reindex",
+  "runtime_store_globs": {
+    "codex": "*.jsonl",
+    "claude-code": "*.jsonl",
+    "cursor": "*.jsonl",
+    "cursor-agent": "store.db",
+    "opencode": "opencode.db",
+    "github-copilot": "session-store.db"
+  },
+  "families": [
+    "instruction_document",
+    "history_prompt",
+    "conversation_turn",
+    "tool_call",
+    "project_config_signal"
+  ]
+}

package/bundle/references/adapters/cursor.md

@@ -49,23 +49,24 @@ install steps also live in [`README.md`](../../README.md) and
 This repository dogfoods committed Cursor surfaces:
 
 - `.cursor/hooks.json` — sessionStart env export, preToolUse hard gate, postToolUse advisory validation
-- `.cursor/agents/*.md` — twelve managed capability descriptors
+- `.cursor/agents/agentera.md` — single managed agent descriptor (D73)
 - `.cursor-plugin/plugin.json` — marketplace submission-ready manifest
 
-Hooks resolve helper scripts through `uv run hooks/...` from the project root.
-`sessionStart` exports `AGENTERA_HOME` through Cursor hook JSON (`env`) before
-subsequent hook executions run.
+Hooks invoke the TypeScript CLI through `npx -y agentera hook …` (or
+`npx -y agentera@next hook …` on the development channel). `sessionStart` exports
+`AGENTERA_HOME` through Cursor hook JSON (`env`) before subsequent hook executions
+run.
 
 ## AGENTERA_HOME wiring
 
-Primary path: `hooks/cursor_session_start.py` resolves the install root from
-`AGENTERA_HOME`, project walk-up, or the plugin/checkout root (`hooks/` parent)
-when the hook runs from a plugin install, then returns
+Primary path: `agentera hook cursor-session-start` resolves the install root from
+`AGENTERA_HOME`, project walk-up, the plugin/checkout root, or the platform default
+app home when env and walk-up do not resolve a managed root, then returns
 `{"env": {"AGENTERA_HOME": "<root>"}}` plus optional `additional_context` from
 the shared session digest.
 
-Fallback: `scripts/setup_cursor.py` reports persistent shell configuration only
-when live shell-tool smoke proves session env does not propagate to CLI
+Fallback: `packages/cli/src/setup/cursor.ts` reports persistent shell configuration
+only when live shell-tool smoke proves session env does not propagate to CLI
 subprocesses. Agentera does not write shell rc files by default.
 
 ## Artifact validation

package/bundle/references/adapters/opencode.md

@@ -1,6 +1,6 @@
 # OpenCode Adapter
 
-Maps agentera's host adapter contract (SPEC.md Section 21) and session corpus contract (SPEC.md Section 22) to OpenCode's specific mechanisms. A developer reading only this document can implement portable-core agentera support and a profilera-compatible session corpus in OpenCode without reading any skill entry file source code.
+Maps agentera's host adapter contract (SPEC.md Section 21) and session corpus contract (SPEC.md Section 22) to OpenCode's specific mechanisms. A developer reading only this document can implement portable-core agentera support and a profile-compatible session corpus in OpenCode without reading any skill entry file source code.
 
 ---
 
@@ -17,7 +17,7 @@ Status: production reference (formerly design document).
 | Skill install | Documented below | `npx skills add jgabor/agentera -g -a opencode --skill agentera -y` |
 | Profile path | Documented below | `~/.config/opencode/profile/PROFILE.md` |
 
-Routes exact bare text hej through chat.message to the bundled Agentera dashboard path. The public docs page omits this hook, but `packages/plugin/src/index.ts` defines `"chat.message"` on the exported `Hooks` interface.
+Routes exact bare text /agentera through chat.message to the bundled Agentera dashboard path. The public docs page omits this hook, but `packages/plugin/src/index.ts` defines `"chat.message"` on the exported `Hooks` interface.
 
 The plugin was promoted from `references/adapters/opencode-plugin.js` to `.opencode/plugins/agentera.js` and is now the production local-file location. Install it with:
 
@@ -56,7 +56,7 @@ OpenCode skill search paths:
 - Global install: `npx skills add jgabor/agentera -g -a opencode --skill agentera -y`
 - Project install: symlink or copy `skills/agentera/` into `.opencode/skills/agentera/` or `.agents/skills/agentera/`
 
-Each Agentera skill entry file contains YAML frontmatter with `name` and `description`, which matches OpenCode's frontmatter requirements exactly. The OpenCode plugin adds one prompt transformation: when the complete user message is exactly bare text `hej`, `chat.message` rewrites it to load the bundled `agentera` skill and route through the `agentera prime` dashboard path. The match is exact except for OpenCode's CLI-added single trailing newline transport artifact, and does not apply to `Hej`, `hej there`, attachments, or other message parts.
+Each Agentera skill entry file contains YAML frontmatter with `name` and `description`, which matches OpenCode's frontmatter requirements exactly. The OpenCode plugin adds one prompt transformation: when the complete user message is exactly bare text `/agentera`, `chat.message` rewrites it to load the bundled `agentera` skill and route through the `agentera prime` dashboard path. The match is exact except for OpenCode's CLI-added single trailing newline transport artifact, and does not apply to `/agentera plan`, `/agentera status`, attachments, or other message parts.
 
 **OpenCode frontmatter validation** requires: `name` (1-64 chars, lowercase alphanumeric with single hyphens), `description` (1-1024 chars). Agentera entry point names are lowercase, matching the validation regex `^[a-z0-9]+(-[a-z0-9]+)*$`.
 
@@ -82,14 +82,14 @@ Each Agentera skill entry file contains YAML frontmatter with `name` and `descri
 
 **Adapter approach**: Place PROFILE.md at `~/.config/opencode/profile/PROFILE.md` (or `~/.config/opencode/PROFILE.md` for simplicity). Update the profile-path references:
 
-- Skills reference `$PROFILERA_PROFILE_DIR/PROFILE.md` (default: `$XDG_DATA_HOME/agentera/PROFILE.md`) with `<!-- platform: profile-path -->` annotations
+- Skills reference `$AGENTERA_PROFILE_DIR/PROFILE.md` (default: `$XDG_DATA_HOME/agentera/PROFILE.md`) with `<!-- platform: profile-path -->` annotations
 - The OpenCode adapter substitutes `~/.config/opencode/profile/PROFILE.md`
-- Profilera writes to this path when generating the profile
+- Profile writes to this path when generating the profile
 
 **Concrete substitution**: In contract.md files, the annotated line:
 
 ```
-Read PROFILE.md from the profilera-determined profile path (`$PROFILERA_PROFILE_DIR/PROFILE.md`, defaulting to `$XDG_DATA_HOME/agentera/PROFILE.md` on Linux). <!-- platform: profile-path -->
+Read PROFILE.md from the profile-determined profile path (`$AGENTERA_PROFILE_DIR/PROFILE.md`, defaulting to `$XDG_DATA_HOME/agentera/PROFILE.md` on Linux). <!-- platform: profile-path -->
 ```
 
 becomes in the OpenCode context:
@@ -112,14 +112,14 @@ Read PROFILE.md from the runtime-provided profile path (Section 21). In OpenCode
 
 **Adapter approach**: Map agentera's worktree isolation to one of two strategies:
 
-**Strategy A: Managed descriptor dispatch (recommended for current port)**
+**Strategy A: Single agent dispatch (D73)**
 
-- Define Agentera's dispatched capabilities as OpenCode subagents
-- Each capability gets a managed markdown file in `.opencode/agents/`
-- Descriptor frontmatter stays within documented OpenCode agent fields: `description` and `mode: subagent`; the file name supplies the agent name.
-- Agentera ownership is recorded in a body comment marker, not custom frontmatter, so unknown options are not passed through as model options.
-- The OpenCode plugin copies those descriptors to `~/.config/opencode/agents/` on startup and preserves user-owned collisions
-- The orchestrating skill (realisera, orkestrera) uses `@<capability>` to invoke work
+- A single Agentera primary agent (`agentera.md`) in `.opencode/agents/`
+- The agent loads the Agentera skill for routing, runs `agentera prime --context <capability> --format json` to fetch instructions, then dispatches to a built-in `general` subagent
+- Descriptor frontmatter uses `description` and `mode: primary` with broad `permission` (write+bash allow)
+- Agentera ownership is recorded in a body comment marker
+- The OpenCode plugin copies the agent descriptor to `~/.config/opencode/agents/` on startup
+- The orchestrating skill (build, orchestrate) uses `@agentera` to invoke work
 - Limitation: runs in the same working tree, not isolated. Suitable for non-destructive work.
 
 **Strategy B: Manual git worktree (full isolation parity)**
@@ -130,18 +130,18 @@ Read PROFILE.md from the runtime-provided profile path (Section 21). In OpenCode
 - Provides true parallel implementation with independent branches
 - Requires explicit orchestration in the skill workflow
 
-**Concrete mapping for realisera Step 5 dispatch**:
+**Concrete mapping for build Step 5 dispatch**:
 
 ```
 # Claude Code (reference)
 Spawn a Sonnet implementation agent in a worktree (isolation: "worktree")
 
 # OpenCode Strategy A
-Invoke the relevant managed capability descriptor, for example @realisera, with the implementation plan
+Invoke the Agentera agent (@agentera) with the implementation plan
 
 # OpenCode Strategy B
 git worktree add ../worktree-branch branch-name
-Dispatch the relevant managed descriptor with cwd set to ../worktree-branch
+Dispatch @agentera with cwd set to ../worktree-branch
 After completion: git merge, git worktree remove
 ```
 
@@ -182,7 +182,7 @@ opencode serve --port 4096
 |-------------|----------|
 | `claude -p "prompt"` | `opencode run "prompt"` |
 | `claude -p --output-format json` | `opencode run --format json "prompt"` |
-| `claude -p --skill realisera` | `opencode run "prompt"` (skill loaded via discovery) |
+| `claude -p --skill build` | `opencode run "prompt"` (skill loaded via discovery) |
 
 The agentera eval runner (`scripts/eval_skills.py`) would need an OpenCode dispatch mode that calls `opencode run --format json` instead of `claude -p --output-format json`. The dispatch wrapper:
 
@@ -207,10 +207,10 @@ def dispatch_opencode(skill_name: str, prompt: str) -> dict:
 |---------------|----------------|-------|
 | SessionStart | `event` hook with `event.type === "session.created"` | Observation only unless a supported context-injection hook is also used |
 | Stop | `event` hook with `event.type === "session.idle"` | Fires when a session reaches idle state |
-| Exact bare `hej` | `chat.message` | Rewrites only the complete text message `hej` so the bundled `agentera` skill owns the dashboard path |
+| Exact bare `/agentera` | `chat.message` | Rewrites only the complete text message `/agentera` so the bundled `agentera` skill owns the dashboard path |
 | PreToolUse | `tool.execute.before` | Blocks invalid reconstructable artifact candidates by throwing an error |
 | PostToolUse | `tool.execute.after` | Fires after every tool execution |
-| Compaction context | `experimental.session.compacting` | Appends bounded Agentera state from `agentera hej --format json` |
+| Compaction context | `experimental.session.compacting` | Appends bounded Agentera state from `agentera prime --format json` |
 
 OpenCode plugins subscribe to session events by exporting one generic `event` hook:
 
@@ -233,7 +233,7 @@ export const AgenteraPlugin = async ({ project, client, $, directory, worktree }
       // PostToolUse equivalent: report validation warnings
     },
     "chat.message": async (input, output) => {
-      // Exact bare hej prompt rewrite.
+      // Exact bare /agentera prompt rewrite.
     },
     "experimental.session.compacting": async (input, output) => {
       // Append bounded Agentera CLI state context.
@@ -248,17 +248,17 @@ Install-root semantics used by the plugin are contract-bound to `scripts/install
 
 OpenCode runtime facts are owned by the RuntimeAdapter registry at `references/adapters/runtime-adapter-registry.yaml` and loaded through `scripts/runtime_adapter_registry.py`. This reference describes the OpenCode adapter behavior, but registry-owned values such as event support, artifact-validation claims, config targets, diagnostic labels, and documentation claims must be validated against the registry rather than changed here as an independent source. The install-root Module must keep package manifest registry and package metadata consolidation work outside its scope.
 
-Registry parity claims: Blocks invalid reconstructable artifact candidates. Routes exact bare text hej through chat.message to the bundled Agentera dashboard path.
+Registry parity claims: Blocks invalid reconstructable artifact candidates. Routes exact bare text /agentera through chat.message to the bundled Agentera dashboard path.
 
 1. **SessionStart** (`event.type === "session.created"`): Observe session creation through the event hook. Session-start context preload remains deferred because no supported model-context injection path is verified for this adapter. Do not attach dead preload code to event observation alone.
 
 2. **PreToolUse** (`tool.execute.before`): When `write` or `edit` args expose a path plus candidate content or exact replacement evidence, validate the candidate through `hooks/validate_artifact.py`. Throw an error to block invalid artifact content before mutation. Sparse payloads and `apply_patch` `patchText` without reconstructed full content are allowed rather than guessed.
 
-3. **Exact bare `hej`** (`chat.message`): If the incoming user message has exactly one meaningful text part and that text is exactly `hej` after removing only OpenCode's CLI-added single trailing newline transport artifact, replace that text with an Agentera routing prompt that preserves the original-message fact and instructs the agent to run `agentera hej` instead of replying with a generic greeting. This is intentionally not a broad greeting detector.
+3. **Exact bare `/agentera`** (`chat.message`): If the incoming user message has exactly one meaningful text part and that text is exactly `/agentera` after removing only OpenCode's CLI-added single trailing newline transport artifact, replace that text with an Agentera routing prompt that preserves the original-message fact and instructs the agent to run `agentera prime` instead of replying with a generic greeting. This is intentionally not a broad greeting detector.
 
 4. **PostToolUse** (`tool.execute.after`): After `write` or `edit`, run the shared artifact validator for warnings. This is advisory because the mutation already happened.
 
-5. **Compaction context** (`experimental.session.compacting`): Before OpenCode compacts a session, append a bounded Agentera project-state summary generated by `agentera hej --format json`. This hook is CLI-first by design and does not read `.agentera` artifacts directly.
+5. **Compaction context** (`experimental.session.compacting`): Before OpenCode compacts a session, append a bounded Agentera project-state summary generated by `agentera prime --format json`. This hook is CLI-first by design and does not read `.agentera` artifacts directly.
 
 6. **Stop** (`event.type === "session.idle"`): Append a runtime-local bookmark entry under the Agentera data directory capturing artifact changes for next-session continuity.
 
@@ -336,7 +336,7 @@ The SDK exposes message history with timestamps, project context, and session me
 1. Enumerate sessions via `opencode session list --format json`
 2. Export each session via `opencode export [sessionID]`
 3. Filter for user-originated messages from the export JSON
-4. Apply decision-pattern regex (same patterns profilera uses for Claude Code history) to classify prompts as `"decision"`, `"correction"`, or `"question"`
+4. Apply decision-pattern regex (same patterns profile uses for Claude Code history) to classify prompts as `"decision"`, `"correction"`, or `"question"`
 5. Produce history_prompt records with session and project metadata
 
 ```python
@@ -438,7 +438,7 @@ Summary of which corpus families the OpenCode adapter can produce:
 | Conversation exchanges | conversation_turn | Yes (CLI) | `opencode export [sessionID]` provides full session JSON with paired user-assistant turns |
 | Config patterns | project_config_signal | Yes | Direct filesystem scan, identical to Claude Code |
 
-**Initial port profilera mode**: Full. All four source families are available via included OpenCode functionality. Crystallized decisions come from AGENTS.md files and instructions config. Decision history and conversation exchanges come from `opencode export` CLI output. Config patterns come from direct filesystem scan.
+**Initial port profile mode**: Full. All four source families are available via included OpenCode functionality. Crystallized decisions come from AGENTS.md files and instructions config. Decision history and conversation exchanges come from `opencode export` CLI output. Config patterns come from direct filesystem scan.
 
 ---
 
@@ -510,7 +510,7 @@ OpenCode repair is ownership-gated. Managed slash commands include `agentera_man
 
 | Gap | Impact | Mitigation |
 |-----|--------|------------|
-| Sub-agent dispatch lacks built-in worktree isolation | realisera/orkestrera run in same working tree | Strategy A (Task tool) for initial port; manual `git worktree` commands for full isolation |
+| Sub-agent dispatch lacks built-in worktree isolation | build/orchestrate run in same working tree | Strategy A (Task tool) for initial port; manual `git worktree` commands for full isolation |
 | `opencode run --format json` event schema differs from `claude -p --output-format json` | Eval runner needs a separate JSON event parser | Implement an OpenCode-specific parser module in eval_skills.py; event stream structure is straightforward |
 | Session history requires JSON event schema mapping | history_prompt and conversation_turn need export parser | `opencode export [sessionID]` provides full session JSON; adapter parses the export output |
 | Python scripts require Python runtime | Hook plugin calls Python via shell | Python is already a prerequisite for agentera scripts |

package/bundle/references/adapters/runtime-adapter-characterization.md

@@ -39,7 +39,7 @@ Characterized runtime actions:
 | Codex CLI | `copy-agent` | `~/.codex/agents/*.toml` | `pending` | copies managed capability descriptors, then reports `runtime update applied` |
 | Copilot CLI | `configure` | none | `noop` | no local config write; use per-invocation `AGENTERA_HOME` |
 | OpenCode | `copy-plugin` | `~/.config/opencode/plugins/agentera.js` | `pending` | copies plugin, then reports `runtime update applied` |
-| OpenCode | `copy-agent` | `~/.config/opencode/agents/*.md` | `pending` | copies managed capability descriptors, then reports `runtime update applied` |
+| OpenCode | `copy-agent` | `~/.config/opencode/agents/agentera.md` | `pending` | copies single managed agent descriptor (D73), then reports `runtime update applied` |
 
 Package-phase items currently expose `runtime`, `action`, `command`, `status`,
 and `message`. Without `--update-packages`, package items are `skipped`; with it,

package/bundle/references/adapters/runtime-adapter-registry.yaml

@@ -125,12 +125,12 @@ records:
       payload_reconstruction_limitations:
         - Sparse payloads and apply_patch patchText without reconstructed full content are allowed.
     subagent_dispatch:
-      mechanism: OpenCode .opencode/agents descriptors
+      mechanism: OpenCode .opencode/agents single primary agent (D73)
       setup_targets:
         - ~/.config/opencode/agents
       descriptor_sources:
-        - .opencode/agents/*.md
-      invocation_pattern: Use @<capability> for the installed Agentera capability descriptor.
+        - .opencode/agents/agentera.md
+      invocation_pattern: Use @agentera for the single Agentera primary agent; routing via skill, dispatch to general subagent.
       tool_configuration: per_agent_permission
       limitations:
         - OpenCode descriptor bootstrap is file-based and preserves user-owned descriptor collisions.
@@ -152,6 +152,8 @@ records:
         - opencode_managed_commands
         - opencode_skill_paths
         - bundled_support_references
+        - profile_dir_deprecated
+        - profile_dir_schema_literal
       status_labels:
         - pass
         - warn
@@ -174,13 +176,17 @@ records:
         - OpenCode Agentera skill paths are missing or broken
         - bundled support references validate separately from installer status
         - bundled reference validation mismatch found despite installer status
+        - profile dir env var is current
+        - v2 env var PROFILERA_PROFILE_DIR detected; run `agentera upgrade` to migrate to AGENTERA_PROFILE_DIR
+        - OpenCode plugin profile-dir schema is current
+        - OpenCode plugin source uses unmigrated profile-dir schema literal (PROFILERA_PROFILE_DIR without AGENTERA_PROFILE_DIR); run `agentera upgrade`
     documentation_claims:
       reference_paths:
         - references/adapters/runtime-feature-parity.md
         - references/adapters/opencode.md
       parity_claims:
         - Blocks invalid reconstructable artifact candidates.
-        - Routes exact bare text hej through chat.message to the bundled Agentera dashboard path.
+        - Routes exact bare text /agentera through chat.message to the bundled Agentera dashboard path.
       install_claims:
         - OpenCode plugin is copied to the native plugin path.
       known_drifts:
@@ -217,7 +223,7 @@ records:
         postToolUse: supported
         errorOccurred: supported
       limitations:
-        - Profilera exposes bounded corpus metadata limits with missing source families.
+        - Profile exposes bounded corpus metadata limits with missing source families.
     artifact_validation:
       validation_events:
         - preToolUse
@@ -397,7 +403,7 @@ records:
         stop: supported
       limitations:
         - Cloud agents are unsupported in v1; repo hooks and managed agents target local IDE sessions only.
-        - Bare text hej routing is metadata-only; sessionStart injects context but does not rewrite prompts.
+        - Bare text /agentera routing is metadata-only; sessionStart injects context but does not rewrite prompts.
     artifact_validation:
       validation_events:
         - preToolUse
@@ -406,12 +412,12 @@ records:
       payload_reconstruction_limitations:
         - Malformed, sparse, or non-reconstructable tool_input payloads are allowed.
     subagent_dispatch:
-      mechanism: Cursor .cursor/agents descriptors
+      mechanism: Cursor .cursor/agents single agent descriptor (D73)
       setup_targets:
         - .cursor/agents
       descriptor_sources:
-        - .cursor/agents/*.md
-      invocation_pattern: Use the Cursor agent picker or @-mention the installed Agentera capability descriptor.
+        - .cursor/agents/agentera.md
+      invocation_pattern: Use the Cursor agent picker or @-mention the single Agentera agent; routing via skill, dispatch to general subagent.
       tool_configuration: global_full_access
       limitations:
         - Cloud agent sessions do not load project hooks or managed agents in v1.
@@ -545,4 +551,4 @@ records:
         - cursor-agent inherits IDE hook wiring only when run inside a workspace with installed Cursor surfaces.
       known_drifts:
         - CLI hook and session env parity is degraded relative to Cursor IDE.
-        - Bare text hej routing is metadata-only like Claude, Copilot, and Codex.
+        - Bare text /agentera routing is metadata-only like Claude, Copilot, and Codex.

package/bundle/references/adapters/runtime-feature-parity.md

@@ -75,10 +75,10 @@ before mutation.
 | Runtime | Dispatch surface | Descriptor source | Tool Access | Verification surface |
 |---------|------------------|-------------------|-------------|----------------------|
 | Claude Code | Native Task/subagent surface | Host-managed; no Agentera descriptor files shipped for this phase | None (no descriptors) | RuntimeAdapter registry |
-| OpenCode | `@<capability>` descriptors under `~/.config/opencode/agents` | `.opencode/agents/*.md`, bootstrapped by `.opencode/plugins/agentera.js` | Per-agent `permission` frontmatter | `scripts/smoke_opencode_bootstrap.mjs`, `agentera validate descriptors` |
+| OpenCode | Single `agentera` primary agent with `general` subagent dispatch | `.opencode/agents/agentera.md`, bootstrapped by `.opencode/plugins/agentera.js` | Per-agent `permission` frontmatter (broad: write+bash allow) | `scripts/smoke_opencode_bootstrap.mjs`, `agentera validate descriptors` |
 | Copilot CLI | User-driven host action such as `/fleet` when available | Host-managed; no Agentera descriptor files shipped for this phase | N/A (no descriptors) | RuntimeAdapter registry |
 | Codex CLI | Native agent descriptors under `~/.codex/agents` or project `.codex/agents` with bounded `[agents]` settings | `skills/agentera/agents/*.toml`, installed by `scripts/setup_codex.py` and `agentera upgrade` | Global sandbox policy (no per-agent) | `agentera validate descriptors`, `tests/test_setup_codex.py`, `tests/test_upgrade_cli.py` |
-| Cursor IDE | Cursor agent picker / @-mention for managed capability descriptors | `.cursor/agents/*.md`, via local plugin or `agentera upgrade --runtime cursor` | Global full access (no per-agent) | `references/adapters/cursor.md`, `scripts/validate_lifecycle_adapters.py`, `tests/test_upgrade_cli.py` |
+| Cursor IDE | Single `agentera` agent with `general` subagent dispatch | `.cursor/agents/agentera.md`, via local plugin or `agentera upgrade --runtime cursor` | Global full access (no per-agent) | `references/adapters/cursor.md`, `scripts/validate_lifecycle_adapters.py`, `tests/test_upgrade_cli.py` |
 | Cursor Agent CLI | Host-managed `cursor-agent -p` print mode | Workspace `.cursor/agents/*.md` when present; no separate CLI descriptor install | Global full access (no per-agent) | `scripts/eval_skills.py --runtime cursor-agent`, `tests/test_eval_skills.py` |
 
 Agentera v2 does not write legacy `[agents.<name>]` Codex config blocks. Capability dispatch must use runtime-native subagent descriptors or host Task surfaces, not unsupported `agentera <capability>` CLI commands.

package/bundle/references/analysis/benchmark.md

@@ -121,7 +121,7 @@ Follow this loop:
    by `raw_artifact_access_after_cli_counts` when the read is not redundant yet
    but still happens after a successful CLI state call.
 4. Map each repeated raw read to the CLI state owner. Prefer enriching existing
-   routine commands or the `hej` composite startup result. Do not add Decision 43
+    routine commands or the `prime` composite startup result. Do not add Decision 43
    slash-route aliases as CLI commands.
 5. Make CLI completeness explicit. A startup-capable response should say whether
    it is complete for the requested capability, whether raw artifact reads are

package/bundle/references/analysis/startup-measurement-contract.yaml

@@ -90,16 +90,16 @@ runtime_extraction_contract:
         parsing encountered schema errors. This is extraction failure evidence,
         not a successful zero-record benchmark window.
       required_counts:
-        - candidate_count when discovery can count candidates
+        - file_count when discovery can count store files
         - record_count, which may be zero or partial
         - error_count greater than zero
       current_examples:
         - runtime: claude-code
-          candidate_count: 4836
+          file_count: 4836
           record_count: 0
           error_count: 2
         - runtime: github-copilot
-          candidate_count: 1
+          file_count: 1
           record_count: 0
           error_count: 1
     no_matching_records:
@@ -110,7 +110,7 @@ runtime_extraction_contract:
         shape, but no supported message or tool records were extracted. This is
         sparse coverage evidence and remains distinct from schema divergence.
       required_counts:
-        - candidate_count when discovery can count candidates
+        - file_count when discovery can count store files
         - "record_count: 0"
         - no error_count greater than zero
     successful_zero_record_window:
@@ -312,8 +312,8 @@ state_gathering_sequence:
   start_anchor: first_agentera_state_call_after_capability_related_user_turn
   capability_invocation_markers:
     - slash route such as /agentera plan or /agentera build
-    - bare capability name such as planera, resonera, or orkestrera
-    - natural-language capability mention such as run orkestrera
+    - bare capability name such as plan, discuss, or orchestrate
+    - natural-language capability mention such as run orchestrate
     - assistant capability intro marker
   end_anchors:
     - first_implementation_boundary
@@ -324,7 +324,7 @@ state_gathering_sequence:
 
 counted_event_classes:
   - class: cli_state_call
-    description: Agentera state CLI reads such as hej, todo, docs, plan, progress, decisions, health, and query.
+    description: Agentera state CLI reads such as prime, todo, docs, plan, progress, decisions, health, and query.
   - class: raw_artifact_access
     description: Direct read, grep, or glob access to Agentera state artifacts after CLI state access.
   - class: capability_prose_read

package/bundle/references/artifacts/artifact-registry-interface-model.yaml

@@ -204,9 +204,10 @@ explicit_special_cases:
     display_name: PROFILE.md
     artifact_type: global_user_state
     scope: global_user_state
-    default_path: $PROFILERA_PROFILE_DIR/PROFILE.md
+    default_path: $AGENTERA_PROFILE_DIR/PROFILE.md
     path_template:
       env_precedence:
+        - AGENTERA_PROFILE_DIR
         - PROFILERA_PROFILE_DIR
         - XDG_DATA_HOME/agentera
         - ~/.local/share/agentera
@@ -235,11 +236,11 @@ explicit_special_cases:
     display_name: benchmark_context
     artifact_type: cli_context
     scope: cli_context
-    default_path: agentera prime --context optimera --format json#benchmark_context
+    default_path: agentera prime --context optimize --format json#benchmark_context
     producers:
       - agentera
     consumers:
-      - optimera
+      - optimize
     docs_yaml_can_override_path: false
 consumer_permissions:
   cross_capability_validator:

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

@@ -229,7 +229,7 @@ structured_output:
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
@@ -589,7 +589,7 @@ field_selection:
         - profile
         - v1_migration
         - health
-        - issues
+        - todo
         - plan
         - docs
         - progress
@@ -880,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
@@ -900,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.
@@ -155,7 +155,7 @@ operation_verbs:
     lifecycle_allowed: false
 consumer_order:
   - doctor
-  - hej
+  - status
   - upgrade
   - docs
   - tests
@@ -176,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/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

@@ -7,3 +7,7 @@ warning:
     - 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.