agentera 3.0.0-dev.6 → 3.0.0-next.1

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

@@ -52,20 +52,21 @@ This repository dogfoods committed Cursor surfaces:
 - `.cursor/agents/*.md` — twelve managed capability descriptors
 - `.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/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:

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/update-channels.yaml

@@ -64,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

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

@@ -150,10 +150,12 @@ decision_44:
       boundary: Preserve capability IDs, artifact IDs, group IDs, route IDs, and test fixture IDs unless a migration is planned.
     - surface: CLI labels and exit behavior
       boundary: Preserve current command names, parseable labels, exit codes, and source-contract labels unless an explicit CLI migration is recorded.
-    - surface: Canonical capability names
-      boundary: Preserve hej, visionera, resonera, inspirera, planera, realisera, optimera, inspektera, dokumentera, profilera, visualisera, and orkestrera.
-    - surface: Decision 43 aliases
-      boundary: Preserve /agentera status, vision, discuss, research, plan, build, optimize, audit, document, profile, design, and orchestrate.
+    - surface: Canonical capability names (v3 surface)
+      boundary: >-
+        Preserve the Decision 43 English alias set as the binding canonical names for v3 and onward: status, vision, discuss, research, plan, build, optimize, audit, document, profile, design, orchestrate. Future capability additions follow the same transfer-friendly English-verb pattern (Decision 70). Per Decision 70, the D43 alias set is the binding name set; future renames require a new decision.
+    - surface: Legacy Swedish capability names (v2 stable only)
+      boundary: >-
+        Preserve hej, visionera, resonera, inspirera, planera, realisera, optimera, inspektera, dokumentera, profilera, visualisera, and orkestrera for the v2 stable distribution (`npx -y agentera@latest`, ships from `main`) and as historical references in archived plans, decisions, and changelogs. Out of scope for v3 surface per Decision 70. Coexistence probe surfaces per-distribution naming divergence.
     - surface: Historical artifacts
       boundary: Do not rewrite old progress, changelog, archived plans, or decisions solely for vocabulary cleanup.
     - surface: Release version