agentera 3.0.0-dev.72 → 3.0.0-dev.74

package/README.md

@@ -112,6 +112,117 @@ reports full, summary-only, or unavailable detail without fabricating archives.
 See [UPGRADE.md](../../UPGRADE.md) for ownership, recovery, and migration
 details.
 
+## Private personal glossary candidate reads
+
+The user-local candidate projection has a separate read-only surface. It does
+not need a project checkout and never reads a project glossary.
+
+```bash
+npx -y agentera@next report personal-glossary-candidates list --limit 20 --format json
+npx -y agentera@next report personal-glossary-candidates get \
+  --candidate-id ID --candidate-revision REVISION \
+  --generation GENERATION --policy-version POLICY --format json
+```
+
+List cursors bind the current generation, policy, filters, limit, order, and
+expiry-aware safe-context availability snapshot. Safe context becomes
+unavailable at its 30-day expiry without changing persisted projection bytes;
+a cursor from an earlier availability view cannot resume. Exact reads return
+opaque validated occurrence identities and a currently available safe context,
+not raw source, anchor, session, project, or filesystem values. Both commands
+are non-interactive and mutation-free.
+
+## Personal glossary decisions
+
+Submit one host semantic classification receipt through the private, read-only
+decision boundary. Copy the current `candidate_projection_sha256` from the
+candidate read into the receipt. The CLI validates the receipt against the
+current projection and evidence, then returns an admission outcome without
+writing a review, profile entry, or project state.
+
+```bash
+npx -y agentera@next report personal-glossary-decision --input receipt.json --format json
+```
+
+Only a current explicit personal definition with a complete resolved
+user-authored anchor can return `automatic_admission`. Inferred candidates stay
+`review_required` or `abstain`, regardless of host confidence. The command does
+not read a project glossary. File and stdin requests are limited to 16,384 UTF-8
+bytes. The machine schema lists the only allowed reason codes for each outcome.
+
+## Personal glossary publication
+
+Publish one current explicit automatic admission through the separate,
+user-local mutation boundary:
+
+```bash
+npx -y agentera@next report personal-glossary-publish --input publication.json --format json
+```
+
+The bounded request contains `schema_version`, `receipt`, `decision`, and
+`as_of`. It can additionally carry an opaque `review_authorization` with a
+review ID and canonical review-record digest. It never accepts a profile or
+project path. Immediately before an atomic replacement, Agentera revalidates the
+current projection, candidate, receipt, CLI decision, evidence, scope, meaning,
+revision, policy, and quality gate. An automatic publication still requires
+`explicit_current_authorized`. A review-required publication additionally needs a
+current stored `accept` or `correct` authorization. The command changes only the
+owned `PROFILE.md` Glossary section and returns opaque bindings, not terms,
+meanings, anchors, paths, or source content. Exact replay with the same date is
+an `unchanged_replay`; malformed, stale, unavailable, or conflicting input leaves
+profile bytes unchanged.
+
+## Personal glossary review records
+
+Queue a current `review_required` decision when no question channel is available.
+The queue takes the same bounded host receipt shape as the decision command and
+revalidates it before writing private metadata.
+
+```bash
+npx -y agentera@next report personal-glossary-reviews queue --input receipt.json --format json
+npx -y agentera@next report personal-glossary-reviews disposition --input disposition.json --format json
+npx -y agentera@next report personal-glossary-reviews list --status pending --limit 20 --format json
+npx -y agentera@next report personal-glossary-reviews get \
+  --review-id ID --candidate-id ID --candidate-revision REVISION \
+  --generation GENERATION --policy-version POLICY --format json
+```
+
+Records live only under the configured user profile. Queue metadata retains opaque
+candidate, receipt, decision, semantic-fingerprint, scope, policy, reason, and
+lifecycle bindings. A `correct` action can retain only its authority-approved
+corrected meaning in the canonical user-local review record. Records never retain
+a term, excerpt, raw evidence, source, session, project, path, tool content,
+signature, nonce, or host proof.
+
+The local host writes one canonical `trusted-local-host.json` document beside the
+review store. It contains the current-user subject and an Ed25519 SPKI public key.
+Only a fresh `agentera.personalGlossaryReviewApproval.v1` action from
+`agentera-local-host` over `agentera-local-host-ipc`, signed by that key, can
+disposition a queued review. The signed receipt binds the review ID, stable term,
+revision, projection, semantic fingerprint, generation, policy, disposition,
+correction fields, timestamps, and nonce. Exact receipt replay is idempotent;
+reusing a nonce with changed signed content fails before effects.
+
+Canonical v1 pending review stores remain readable through `list` and `get`
+without changing their bytes. Only `disposition` can migrate one valid v1 record.
+It revalidates the current receipt and projection, derives the missing scope from
+that receipt, preserves immutable review bindings, and atomically writes the v2
+lifecycle and replay state. Invalid or ambiguous v1 input leaves the store
+unchanged.
+
+Rejected and deferred records suppress a recurrence with the same stable identity,
+semantic fingerprint, scope, and policy even when only corroborating evidence,
+revision, or generation changes. A meaning, scope, or policy change creates a
+bounded reopened record with a visible reason. Accepted or corrected records return
+an opaque authorization for the separate publish command. They do not publish
+directly. List and exact reads are noninteractive, owner-restricted,
+cursor-bounded, and mutation-free.
+
+Terminal metadata expires after 90 days. The bounded receipt replay index expires
+with each approval receipt. Separate authenticated owner maintenance affects only
+review metadata and replay digests. It does not modify a profile entry, project
+state, candidate projection, or publication result.
+
 ## Contributors
 
 Requires Node.js 22+ and pnpm 10.30.3.

package/bundle/.agentera-build-source.json

@@ -0,0 +1,8 @@
+{
+  "schemaVersion": "agentera.generatedBuildSource.v1",
+  "commit": "15c2b8d04ef350ff9e09bc5f40a0d079aeedc399",
+  "tree": "0e0c77c6fc7da5b3da9b6b92eaa6117e669658ef",
+  "files": 6724,
+  "workingTreeSha256": "634b717f526f20689aa5fa08cf3c268675617f59e56d77e1555b9e49cab07606",
+  "identitySha256": "b94b49cdad8c10a7f99ee0189b1981a8d8f3217b345b7e18e29e1f9a8de3c7ed"
+}

package/bundle/CHANGELOG.md

@@ -18,10 +18,10 @@
 
 ### Changed
 
-- Serialized `feat/v3` integrations now allocate one committed
-  `3.0.0-dev.N+1` version locally, then automatically qualify and publish that
-  exact build to npm `@next`. Stable publication from `main` remains protected
-  by review.
+- Every passing `feat/v3` push now publishes one CI-allocated rolling
+  `3.0.0-dev.N` package to npm `@next` without a metadata-only commit. The
+  bounded workflow builds one isolated tarball, validates and smokes those exact
+  bytes, then publishes them directly. Stable publication remains protected by review.
 - Local staged verification now gives ordinary source changes targeted tests
   and typecheck with two workers in at most 60 seconds. State and documentation
   checks stay under 10 seconds, while specialized and global owners defer to
@@ -39,7 +39,7 @@
   --help` expose the exact `agentera.route_receipt.v1` schema, valid outcomes,
   nullability, compound and UTF-8 span rules, plus a runnable stdin round trip.
 - Development releases now run source checks once before explicit metadata review,
-  reuse valid evidence on resume, and construct or reuse one candidate before
+  reuse valid evidence on resume, and construct or reuse one package artifact before
   separate approval, staged exact-version publication, and forward-only tag
   promotion. Invalid or stale evidence fails before release effects, while the
   review pause performs no metadata, approval, rebuild, or registry action.
@@ -113,32 +113,32 @@
 - Fixed native resource cleanup to replay historical Codex descriptor ownership
   IDs, preserve identity collisions and unowned files, and expose the complete
   retired native-resource vocabulary for v2-only upgrade discovery.
-- Fixed release qualification provenance and isolation. CI approvals now bind
-  the contracted qualification repository, workflow, full branch ref, run, and
+- Fixed release verification provenance and isolation. CI approvals now bind
+  the contracted source verification repository, workflow, full branch ref, run, and
   API-backed head SHA before environment approval or artifact mutation;
   stable shim releases require packaged-input source provenance; retained
   artifacts keep and revalidate mode `0444`; and npm/pnpm probes and mutation
   validation use fresh sanitized state. Added a three-run non-mutating
-  qualification benchmark plus a content-bound, monotonic stage/L2/promote
-  publication envelope with a strict two-minute budget, reconciled timing,
-  replay evidence, and first-failure reporting. Source qualification now runs a
+  package verification benchmark plus a content-bound, monotonic publication envelope
+  with a strict two-minute budget, reconciled timing,
+  replay evidence, and first-failure reporting. Source verification now runs a
   bounded evidence DAG: one generated-overlap execution supplies source,
   package, build, and overlap proof beside isolated stress and typecheck owners,
   followed by a solo performance barrier and concurrent compact and
   capability-contract readers. The solo phase prevents CPU contention from
   invalidating machine-sensitive performance evidence. Failures preserve the
-  first owner, settle overlap safely, block candidate work, and issue no
+  first owner, settle overlap safely, block package construction, and issue no
   receipt. Generated-overlap now receives the
   actual source deadline, reserves bounded cleanup and parent-reconciliation
   time, and removes its generated state after failure. Source receipts now mark
   and validate all nine successful gate outcomes and reject semantic tampering.
   The read-only `source-check` command validates matching source evidence for
-  development preparation and direct diagnosis without running qualification
-  gates or changing repository, candidate, receipt, or registry state.
-  Candidate qualification timing now closes construction before exact-artifact
+  development preparation and direct diagnosis without running verification
+  gates or changing repository, package artifact, receipt, or registry state.
+  Package verification timing now closes construction before exact-artifact
   smoke and reconciles non-overlapping gate intervals with explicit overhead.
   Staging now rejects an absent exact version when the public tag already names
-  that target, before candidate inspection, credentials, or publication.
+  that target, before artifact inspection, credentials, or publication.
 
 - Fixed bare `agentera prime` briefs to compact absolute path diagnostics before
   routing and history evidence, preserving executable plan selection, next-action
@@ -177,8 +177,8 @@
 
 ### Added
 
-- Added `agentera report profile-glossary --input <file|->` for Profile Full
-  personal glossary output in `PROFILE.md`, with bounded
+- Added `npx -y agentera@next report personal-glossary-publish --input <file|-> [--dry-run] --format json`
+  for authorized personal glossary publication in `PROFILE.md`, with bounded
   personal provenance, byte-preserving section replacement, deterministic
   confidence decay and refresh, retained permanence, and no project-glossary
   reads. Discuss, Plan, and Build consume it only through bounded glossary

package/bundle/extract-corpus-parity.json

@@ -1,6 +1,6 @@
 {
   "schema_version": "agentera-extract-corpus-parity-v1",
-  "adapter_version": "agentera-v3-corpus-2",
+  "adapter_version": "agentera-v3-corpus-3",
   "max_sqlite_sessions": 60,
   "max_sqlite_rows": 100000,
   "max_tool_arg_text": 500,

package/bundle/references/adapters/package-publication.json

@@ -2,14 +2,14 @@
   "schemaVersion": "agentera.packagePublication.v2",
   "owner": "repository/package scripts",
   "invariants": {
-    "preparation": "Preparation is pure and registry-independent. Serialized feat/v3 integration preparation requires a clean committed source tree, allocates exactly dev.N+1 locally, sets agentera.gitRef to that source HEAD, and changes only the development manifest for a final metadata commit. The manual readiness preparation path first validates a current normalized source receipt, then accepts an explicit target version and source commit. Stable preparation retains its separate source-provenance contract.",
-    "sourceQualification": "Source qualification never repairs source. It issues a content-addressed receipt only after every declared source gate succeeds against a clean committed tree. A matching receipt is a deterministic local cache, not an authorization boundary.",
-    "candidateQualification": "Candidate qualification validates a current source receipt, constructs one retained immutable tarball with the contract-required retained mode, proves dry-pack observation equivalence, and runs a local exact-artifact smoke in an empty isolated npm state before any registry effect.",
-    "publication": "Registry publication consumes the retained candidate bytes through one measured stage, independent exact-version L2, and promote envelope. Stage and promotion include their required registry convergence and observational checks. The envelope never reconstructs an artifact, reruns source qualification, or rolls a tag back.",
-    "approval": "Registry mutation requires an approval bound to the candidate receipt digest, target version, integrity, package, registry, and tag. A serialized push to feat/v3 may issue the development approval automatically only after the committed dev.N increment, source qualification, candidate qualification, and CI attestation pass. Stable publication retains explicit protected-environment review on main. A push never substitutes for candidate binding.",
+    "preparation": "Preparation is pure and registry-independent. CI allocates rolling development package metadata in an isolated construction tree without changing the checkout. The manual readiness preparation path first validates a current normalized source receipt, then accepts an explicit target version and source commit. Stable preparation retains its separate source-provenance contract.",
+    "sourceQualification": "Source verification never repairs source. It issues a content-addressed receipt only after every declared source gate succeeds against a clean committed tree. A matching receipt is a deterministic local cache, not an authorization boundary.",
+    "candidateQualification": "Package verification validates a current source receipt, constructs one retained immutable tarball with the contract-required retained mode, proves dry-pack observation equivalence, and runs a local exact-artifact smoke in an empty isolated npm state before any registry effect.",
+    "publication": "Registry publication consumes the retained package artifact through one measured stage, independent staged package migration smoke, and promote envelope. Stage and promotion include their required registry convergence and observational checks. The envelope never reconstructs an artifact, reruns source verification, or rolls a tag back.",
+    "approval": "Manual development and stable release machinery requires artifact-bound approval. The routine feat/v3 push path instead derives its immutable version and git ref from the GitHub run and push SHA, validates and smokes the exact isolated tarball, and publishes those bytes directly to next. Stable publication retains explicit protected-environment review on main after the stable workflows land on the default branch.",
     "replay": "A matching exact version, integrity, and required tag state is a successful no-upload replay. Conflicting integrity, an escaped artifact, a stale tag, or any unrecognized registry state fails before mutation.",
     "credentials": "Registry inspection runs before credentials are required. Only the npm mutation child receives a mode-0600 temporary user config. Tool probes and every npm, pnpm, and npx child, including receipt validation during stage and promotion, use isolated user/global config, home, cache, and sanitized npm/pnpm environments.",
-    "output": "Every transaction phase emits a bounded start and end result with package, version, phase, outcome, elapsedMs, executed, reused, and nextAction. The qualified-publication coordinator emits one content-bound timing receipt in JSON or equivalent human output with measured component and total durations, strict budget status, first failure, reconciliation, and replay state. Diagnostics redact credentials and private absolute paths."
+    "output": "Every transaction phase emits a bounded start and end result with package, version, phase, outcome, elapsedMs, executed, reused, and nextAction. The publication coordinator emits one content-bound timing receipt in JSON or equivalent human output with measured component and total durations, strict budget status, first failure, reconciliation, and replay state. Diagnostics redact credentials and private absolute paths."
   },
   "packages": {
     "development": {
@@ -46,26 +46,30 @@
   "ci": {
     "repository": "jgabor/agentera",
     "qualificationWorkflow": {
-      "name": "Qualify release candidate",
-      "path": ".github/workflows/qualify-candidate.yml",
+      "name": "Publish development package",
+      "path": ".github/workflows/qualify.yml",
       "ref": "refs/heads/feat/v3"
     },
     "developmentPush": {
       "trigger": "push to refs/heads/feat/v3",
-      "versionAuthority": "packages/cli/package.json committed by the serialized local feat/v3 integrator",
-      "preparationCommand": "pnpm cli:prepare:dev-push -- --json",
-      "validationCommand": "pnpm cli:validate:dev-push -- --before-commit BEFORE --metadata-commit HEAD --json",
+      "versionAuthority": "GitHub Actions workflow run number plus the fixed migration offset",
+      "runNumberOffset": 72,
       "rules": [
-        "BEFORE must be an ancestor of the source commit",
-        "HEAD must be one non-merge metadata-only commit after the source commit",
-        "source must retain the BEFORE development version",
-        "HEAD must increment dev.N exactly once and set agentera.gitRef to the source commit",
-        "routine CI defers its duplicate release conjunction on direct feat/v3 pushes",
-        "CI never allocates a version or uses github.run_number",
-        "reruns reuse the same version, candidate, and source run identity"
+        "version is 3.0.0-dev.(GITHUB_RUN_NUMBER + 72)",
+        "agentera.gitRef equals GITHUB_SHA",
+        "the checkout manifest is not modified",
+        "one isolated tarball is built, validated for version and git ref, and executable-smoked before those exact bytes are published to next",
+        "reruns reuse the same run number, SHA, and version; identical already-published bytes succeed without another upload",
+        "failed runs can create version gaps",
+        "before the first push, confirm qualify.yml is still unregistered at run 0 and npm 3.0.0-dev.73 is absent"
       ],
-      "approval": "After exact candidate qualification and CI attestation, the workflow issues a machine candidate-bound development approval and publishes to next without a review environment.",
-      "concurrency": "The local integrator waits for the prior development workflow to finish before another push. One non-cancelling workflow group protects the active run; it is not used as an unbounded queue."
+      "approval": "The routine push workflow publishes the locally validated exact tarball to next without the manual qualification, receipt, attestation, benchmark, approval, or artifact-handoff framework.",
+      "concurrency": "The publish-next-${{ github.ref }} group uses queue: max, which keeps up to 100 pending runs and does not cancel an active or pending push."
+    },
+    "stableVerificationWorkflow": {
+      "name": "Verify stable package",
+      "path": ".github/workflows/verify-stable.yml",
+      "ref": "refs/heads/main"
     },
     "publicationRunBinding": {
       "beforeArtifactDownload": [
@@ -80,13 +84,13 @@
         "run.conclusion"
       ],
       "refRule": "qualificationWorkflow.ref is a full refs/heads branch ref; run.head_branch must equal its exact branch name",
-      "beforeEnvironmentApproval": "The content-validated candidate receipt metadataCommit must equal the API-backed run.head_sha"
+      "beforeEnvironmentApproval": "The content-validated package artifact receipt metadataCommit must equal the API-backed run.head_sha; development sourceCommit must also equal run.head_sha"
     }
   },
   "qualification": {
     "source": {
       "component": "release-source",
-      "issuanceAuthority": "A new source receipt can be issued only by the contracted GitHub Actions qualification workflow at the committed checkout SHA. Existing valid receipts remain reusable through the read-only source check.",
+      "issuanceAuthority": "A new source receipt can be issued only by the contracted GitHub Actions source verification workflow at the committed checkout SHA. Existing valid receipts remain reusable through the read-only source check.",
       "inputs": [
         "tracked_tree_except_package_version_gitRef",
         "verification_policy",
@@ -304,16 +308,16 @@
               "sha256": "03fe600a3a27f05daf0d1b59c16b00bedc354a13c70ea60be0b457175fdf743c"
             },
             "reference": {
-              "count": 22,
-              "sha256": "2b48c82bb7ee10388d9ebb4fa7ea3743ea82a7e9aaedfcd5a858eeedb9d891ae"
+              "count": 25,
+              "sha256": "2094946cd6e189c6ab3db16dd0725596cec759abcea88d8335b05215b65ccfc2"
             },
             "state": {
               "count": 38,
               "sha256": "7ab0dd6ef1b1b1ce66bd9ea94d1de3d542528233e928a44102e289bf12416681"
             },
             "package": {
-              "count": 66,
-              "sha256": "3548af7e84151c90690a6eb3d1cb6c7847f39b290161ecab599d8cb1bf0d2cb0"
+              "count": 67,
+              "sha256": "d73cd86fed39057cf9ae73e462a59e842372392b1e88846f2b220378a2ff75cc"
             },
             "bootstrap": {
               "count": 34,
@@ -321,17 +325,17 @@
             }
           },
           "total": {
-            "count": 280,
-            "sha256": "051ed9a57857a39e11ed8fb583bff9d2a67a306c5ab897a0ee829212468bc23a"
+            "count": 284,
+            "sha256": "3f30b26839aec47639f2197c9efda5caf2a73d5afca9fb38ff9a341e18a72b98"
           }
         }
       },
       "reuseCheck": {
         "command": "node packages/cli/scripts/release-qualification.mjs source-check --candidate-dir DIR [--json]",
-        "authority": "The external path is input only. Reuse requires digest, full receipt semantics, exact governed gates, current toolchain, and matching current staged and working tracked-tree identities under the same package version and agentera.gitRef normalization used at source qualification.",
-        "effects": "Runs no qualification gate and writes no repository, candidate, receipt, or registry state. Success emits executed none and reused true without receipt content or private paths.",
-        "fallback": "A missing, invalid, ambiguous, or stale receipt fails before manual readiness metadata effects. Serialized integration preparation and the local staged-verification lane do not consume release receipts.",
-        "scope": "Manual readiness preparation uses the check as a source-readiness prerequisite. Direct diagnostics may inspect reuse without executing a gate. Build, compact, parity, candidate qualification, release metadata, approval, and publication remain mandatory at their owning stages."
+        "authority": "The external path is input only. Reuse requires digest, full receipt semantics, exact governed gates, current toolchain, and matching current staged and working tracked-tree identities under the same package version and agentera.gitRef normalization used at source verification.",
+        "effects": "Runs no verification gate and writes no repository, package artifact, receipt, or registry state. Success emits executed none and reused true without receipt content or private paths.",
+        "fallback": "A missing, invalid, ambiguous, or stale receipt fails before manual readiness metadata effects. Serialized integration preparation and the local staged verification lane do not consume release receipts.",
+        "scope": "Manual readiness preparation uses the check as a source-readiness prerequisite. Direct diagnostics may inspect reuse without executing a gate. Build, compact, parity, package verification, release metadata, approval, and publication remain mandatory at their owning stages."
       },
       "dag": {
         "batchA": ["generated-overlap", "stress", "typecheck"],
@@ -362,8 +366,8 @@
         "source": "source-receipt.json",
         "candidate": "candidate-receipt.json"
       },
-      "reuse": "A present source receipt is validated with the source reuse check instead of invoking source qualification. A present candidate receipt and retained artifact are validated instead of invoking candidate qualification. Invalid, stale, incomplete, or mismatched evidence rejects the run before an issuance owner starts.",
-      "metadataReview": "A successful source qualification or source-receipt reuse pauses before candidate construction until the caller supplies the explicit reviewed metadata commit. The coordinator never prepares metadata, changes a version, commits, approves, rebuilds a valid candidate, stages bytes, or mutates registry state.",
+      "reuse": "A present source receipt is validated with the source reuse check instead of invoking source verification. A present package artifact receipt and retained artifact are validated instead of invoking package verification. Invalid, stale, incomplete, or mismatched evidence rejects the run before an issuance owner starts.",
+      "metadataReview": "A successful source verification or source-receipt reuse pauses before package artifact construction until the caller supplies the explicit reviewed metadata commit. The coordinator never prepares metadata, changes a version, commits, approves, rebuilds a valid package artifact, stages bytes, or mutates registry state.",
       "outcomes": ["paused", "ready", "rejected"],
       "exitCodes": {
         "paused": 0,
@@ -386,7 +390,7 @@
         "artifact_mode"
       ],
       "retainedArtifactMode": "0444",
-      "timing": "Candidate qualification records monotonic, non-overlapping release-metadata, construction/equivalence, and exact-artifact-smoke intervals at their true boundaries. Their sum cannot exceed measured candidate elapsed time; explicit unattributed overhead completes an exact reconciliation.",
+      "timing": "Package verification records monotonic, non-overlapping release-metadata, construction/equivalence, and exact-artifact-smoke intervals at their true boundaries. Their sum cannot exceed measured package verification time; explicit unattributed overhead completes an exact reconciliation.",
       "gates": [
         "release-metadata",
         "dry-pack-observation-equivalence",
@@ -402,7 +406,7 @@
   },
   "trust": {
     "local": "A same-principal source receipt is a deterministic cache only. It cannot authorize registry mutation.",
-    "ci": "CI registry mutation requires the transferred exact artifact and receipts, a CI attestation bound to the candidate receipt and source run, and a candidate-bound approval. The feat/v3 push workflow may issue development approval automatically after every prior bound check passes; stable main publication requires protected-environment review. OIDC provenance is deferred."
+    "ci": "Manual CI publication requires transferred artifacts, receipts, attestation, and artifact-bound approval. The routine feat/v3 push workflow is separate: it validates, smokes, and publishes one local isolated tarball directly. Stable main publication requires protected-environment review. OIDC provenance is deferred."
   },
   "registryStateTable": [
     {
@@ -419,7 +423,7 @@
       "candidateTag": "target version",
       "expectedTag": "older",
       "stage": "replay without upload and run observational smoke",
-      "promote": "move expected tag forward after exact-version qualification"
+      "promote": "move expected tag forward after staged package migration smoke"
     },
     {
       "state": "promoted",
@@ -440,16 +444,16 @@
   ],
   "benchmark": {
     "environment": "Ubuntu runner or clean local Node 22, npm 10, and pnpm 10.30.3; record exact tool versions in receipts.",
-    "fixture": "clean committed checkout and an external empty candidate directory; no tracked or checkout-local generated candidate files.",
-    "cacheNetwork": "Preflight uses no registry call. Every qualification DAG child and each smoke use a distinct empty HOME, npm cache, user config, global config, and report output; public npm dependency network access is allowed and recorded as cold-cache. Publication reads the registry before credentials.",
+    "fixture": "clean committed checkout and an empty external artifact directory; no tracked or checkout-local generated package artifacts.",
+    "cacheNetwork": "Preflight uses no registry call. Every verification DAG child and each smoke use a distinct empty HOME, npm cache, user config, global config, and report output; public npm dependency network access is allowed and recorded as cold-cache. Publication reads the registry before credentials.",
     "repetitions": 3,
-    "statistic": "Qualification reports median wall milliseconds over exactly three cold-cache repetitions. Concurrent owner-duration totals are reported separately; only owners in the same parallel phase overlap, while the solo performance and serial capacity barriers contribute ordered wall time. Phase timing reconciles through measured DAG wall time rather than by summing nested owner durations. Qualified publication reports one actual approved transaction because registry mutation is not a benchmark repetition; replays run the same measured envelope and report reused registry phases.",
-    "coordinator": "packages/cli/scripts/release-benchmark.mjs has separate qualification and publication commands. qualification runs only preflight and source-plus-candidate qualification and never receives npm credentials. publication runs only the approved stage, independent exact-version L2, and promote commands, measures them with one monotonic deadline, and never runs source qualification.",
+    "statistic": "Package verification reports median wall milliseconds over exactly three cold-cache repetitions. Concurrent owner-duration totals are reported separately; only owners in the same parallel phase overlap, while the solo performance and serial capacity barriers contribute ordered wall time. Phase timing reconciles through measured DAG wall time rather than by summing nested owner durations. Publication reports one actual approved transaction because registry mutation is not a benchmark repetition; replays run the same measured envelope and report reused registry phases.",
+    "coordinator": "packages/cli/scripts/release-benchmark.mjs has separate verification and publication commands. verification runs only preflight and source-plus-package verification and never receives npm credentials. publication runs only the approved stage, independent staged package migration smoke, and promote commands, measures them with one monotonic deadline, and never runs source verification.",
     "qualifiedPublication": {
       "command": "node packages/cli/scripts/release-benchmark.mjs publication --adapter ADAPTER --candidate-dir DIR --receipt-file FILE",
       "sequence": [
-        "stage retained bytes on the candidate tag, wait for exact integrity convergence, and observe an isolated exact-version registry smoke",
-        "run an independent exact-version L2 consumer check while the public tag is unchanged",
+        "stage the retained package artifact on the staging tag, wait for exact integrity convergence, and observe an isolated exact-version registry smoke",
+        "run an independent staged package migration smoke while the public tag is unchanged",
         "promote the expected tag forward, wait for tag and integrity convergence, and observe the final exact-version registry smoke"
       ],
       "receiptBindings": [
@@ -462,22 +466,14 @@
         "source_run_id"
       ],
       "timing": "The coordinator measures commands with a monotonic clock. Caller-supplied elapsed data is not accepted. Component floors plus unattributed elapsed time must equal the measured total, and total elapsed time must be strictly less than qualifiedPublicationMs.",
-      "failure": "The first child failure label or timeout owner is retained, later phases do not start, and no rollback is attempted. A retry uses the same exact candidate; stage and promote replay matching registry state without upload or backward tag movement."
+      "failure": "The first child failure label or timeout owner is retained, later phases do not start, and no rollback is attempted. A retry uses the same exact package artifact; stage and promote replay matching registry state without upload or backward tag movement."
     },
     "timeouts": {
       "preflightMs": 30000,
       "sourceQualificationMs": 2400000,
       "qualifiedPublicationMs": 120000
     },
-    "failureRule": "The first observed failing owner remains the reported label. Cancellable peers are stopped, generated-overlap is allowed to settle without forced termination, barrier B and receipt issuance are blocked, and completed/cancelled failures are reported. No timeout or failure authorizes repair, candidate work, or registry mutation.",
-    "workflow": {
-      "path": ".github/workflows/qualification-benchmark.yml",
-      "trigger": "workflow_dispatch only until default-branch scheduling is explicitly authorized",
-      "checkoutRef": "refs/heads/feat/v3",
-      "command": "pnpm cli:benchmark:qualification -- --adapter development --candidate-root DIR --json",
-      "retainedReport": "qualification-benchmark-${{ github.run_id }}",
-      "credentials": "No npm token, approval, publication, stage, promote, or registry mutation path is present."
-    }
+    "failureRule": "The first observed failing owner remains the reported label. Cancellable peers are stopped, generated-overlap is allowed to settle without forced termination, barrier B and receipt issuance are blocked, and completed/cancelled failures are reported. No timeout or failure authorizes repair, package construction, or registry mutation."
   },
   "bounds": {
     "registryAttempts": 6,

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

@@ -48,6 +48,11 @@ records:
         - id: routing-evaluation-corpus
           path: fixtures/routing/hybrid-corpus.yaml
       generated_files:
+        - id: build-source-identity
+          path: .agentera-build-source.json
+          format: json
+          classification: active
+          command_authority_reason: Build-generated source identity binds constructed dist and bundle output to one Git commit, tree, and exact working-tree digest; no source copy exists.
         - id: npx-bundle-marker
           path: .agentera-npx-bundle.json
           format: json
@@ -123,7 +128,6 @@ records:
         - {"path":"CHANGELOG.md","region":"line:160","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"273d7dae87662352c49e5723aaa528efa89c9a7dbc7d43d3cbc54c1a1b9771da","reason":"Changelog line:160 records exact release history for that scalar; it does not direct current execution."}
         - {"path":"CHANGELOG.md","region":"line:162","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"6d02d187f8e271cc6acc4b6966344a841615326891969dbec67815e40a51fe81","reason":"Changelog line:162 records exact release history for that scalar; it does not direct current execution."}
         - {"path":"CHANGELOG.md","region":"line:164","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"a5dd4c79ebfefc03bd1c6e3d159f362fd2c5f584d6ff8de7928edf88414133a9","reason":"Changelog line:164 records exact release history for that scalar; it does not direct current execution."}
-        - {"path":"CHANGELOG.md","region":"line:180","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"7da30a1e06efa386074b418e5d9e935df15398b60c2558c11718c6d7f72453b5","reason":"Changelog line:180 records exact release history for that scalar; it does not direct current execution."}
         - {"path":"CHANGELOG.md","region":"line:190","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"df8119585a79f11d42187fd6f57375401442e761ce94e30dd5a4b280c7a6f9e9","reason":"Changelog line:190 records exact release history for that scalar; it does not direct current execution."}
         - {"path":"CHANGELOG.md","region":"line:198","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"0d5ca59bac58c2171d89e48ba4b9068ff7a8681a852272a09b3a4b28c6edf0a0","reason":"Changelog line:198 records exact release history for that scalar; it does not direct current execution."}
         - {"path":"CHANGELOG.md","region":"line:202","category":"argument_bearing","classification":"exact_exemption","normalized_sha256":"b5dc0e45378318464e595a7ccdbb15acc31ce67a2d55b2a9f8c3f8531c8e6ec7","reason":"Changelog line:202 records exact release history for that scalar; it does not direct current execution."}

package/bundle/references/adapters/package-surface-characterization.md

@@ -56,11 +56,13 @@ checking generated behavior.
 
 [`package-publication.json`](./package-publication.json) owns the shared
 repository publication transaction and distinguishes the development
-TypeScript package from the transitional stable shim. Both require separately
-prepared and committed version and `gitRef` metadata, explicit publication
+TypeScript package from the transitional stable shim. Normal development CI
+derives version and `gitRef` metadata in isolated construction without changing
+the checkout. Manual development recovery and stable publication retain their
+separate prepared metadata paths. Both adapters require explicit publication
 authority, a clean tree, exact registry convergence, safe exact-version replay,
-and bounded phase results. Development retains isolated construction and the
-`next` tag; stable retains shim tests/construction and the `latest` tag. Each
+and bounded phase results. Development uses the `next` tag; stable retains shim
+tests/construction and the `latest` tag. Each
 adapter's only publication smoke is its non-mutating, no-project exact-version
 `--version` invocation, so publication does not absorb migration coverage.
 

package/bundle/references/analysis/evidence-tier-authority.yaml

@@ -72,7 +72,10 @@ tiers:
       optional:
         - project_path
         - session_id
-        - conversation_key
+         - conversation_key
+         - origin_id
+         - content_fingerprint
+         - author_class
     source_identity_rule: >-
       `source_id` is the stable, content-addressable identity of one full
       record. It is derived deterministically from source kind and source parts
@@ -99,11 +102,16 @@ tiers:
         - timestamp
         - project_id
         - runtime
+        - source_class
         - source_product
+        - active_runtime
         - evidence_anchor
       optional:
         - conversation_key
         - session_id
+        - origin_id
+        - content_fingerprint
+        - author_class
     derivation_rule: >-
       The signal tier is a pure function of the full-evidence tier: identical
       inputs produce identical signal membership and ordering. It never stores
@@ -228,6 +236,35 @@ signal_semantics:
         severs the citation chain.
       derivable_from: signal record evidence_anchor -> full_evidence source_id
       consumer: glossary
+    session_id:
+      meaning: >-
+        The stable session identity needed to distinguish independent
+        conversation origins without exposing a raw session transcript.
+      derivable_from: conversation_turn session_id
+      consumer: glossary
+    origin_id:
+      meaning: >-
+        The stable, content-addressed identity of the source that originally
+        supplied transported content. It distinguishes one original
+        instruction origin from transcript copies without retaining the raw
+        source label.
+      derivable_from: explicit adapter transport provenance or session origin
+      consumer: glossary
+    content_fingerprint:
+      meaning: >-
+        A lowercase SHA-256 fingerprint of the source content used to prevent
+        copied or repeated conversation text from counting as independent.
+      derivable_from: source record content
+      consumer: glossary
+    author_class:
+      meaning: >-
+        The source author class, such as user, agent, or injected instruction,
+        used to keep agent-authored text from establishing personal terminology.
+      derivable_from: >-
+        explicit original author provenance when origin_id is transported;
+        otherwise conversation_turn actor metadata when no transported origin
+        is claimed
+      consumer: glossary
   preservation_rule: >-
     Fixing the contract must not remove the required meaning of any kind above
     from current consumers. Personal glossary synthesis is named here because it
@@ -313,6 +350,10 @@ consumer_map:
         - record_identity
         - date
         - evidence_anchor
+        - session_id
+        - origin_id
+        - content_fingerprint
+        - author_class
       rule: >-
         Personal glossary synthesis actively consumes bounded personal-history
         signals. Project-file provenance remains repository evidence under the
@@ -440,7 +481,7 @@ compatibility_states:
       reason: oversized
       outcome: degrade
       recovery: >-
-        Refresh bounded tiers with `npx -y agentera@next stats refresh --consent
+        Refresh bounded tiers with `npx -y agentera@next report refresh --consent
         local-history` or read the signal tier, which is bounded to fit. Do not
         attempt to load the oversized artifact whole.
       determinism: >-
@@ -454,7 +495,7 @@ compatibility_states:
       reason: legacy_monolithic_state
       outcome: degrade
       recovery: >-
-        Emit deterministic refresh guidance: run `npx -y agentera@next stats refresh
+        Emit deterministic refresh guidance: run `npx -y agentera@next report refresh
         --consent local-history` to publish bounded tiers. Legacy monolithic
         state receives refresh guidance rather than indefinite read
         compatibility.
@@ -467,7 +508,7 @@ compatibility_states:
       reason: no_evidence
       outcome: degrade
       recovery: >-
-        Report `npx -y agentera@next stats refresh --consent local-history` and the
+        Report `npx -y agentera@next report refresh --consent local-history` and the
         `--corpus PATH` override. Must not auto-build, scan home directories, or
         run live extraction without consent.
       determinism: >-