agentera 3.0.0-dev.75 → 3.0.0-dev.77

package/README.md

@@ -78,6 +78,15 @@ Preview has no side effects. The apply path is the explicit, one-way v2-to-v3
 migration described in [UPGRADE.md](../../UPGRADE.md); it does not run a native
 package installer.
 
+Agentera product v1 is unsupported. V3 does not migrate or preserve v1 state.
+If product-v1 evidence is detected, ordinary commands stop without mutation and
+the upgrade guide's separate `--reset-product-v1` workflow is the only
+continuation. Its reviewed apply deletes all Agentera state in the listed
+project, profile, installation, and runtime scopes with no backup or restore.
+That reset is destructive and irreversible. It does not replace the supported
+v2-to-v3 migration above. Current schema identifiers ending in `.v1` remain
+valid and do not identify product v1.
+
 Native Agentera resource cleanup is intentionally separate from host support:
 
 ```bash
@@ -114,6 +123,20 @@ details.
 
 ## Private personal glossary candidate reads
 
+An explicitly consented refresh is the production candidate producer:
+
+```bash
+npx -y agentera@next report refresh --consent local-history
+```
+
+After publishing bounded evidence, the same refresh mines explicit and recurring
+signals and writes one private projection bound to that evidence generation.
+Candidate-list summaries include fixed-key aggregate candidate and abstention
+counts for each mining family. They do not expose rejected terms, sources,
+anchors, projects, paths, or excerpts. If projection publication fails, the
+evidence remains current and the nonzero response gives the same consented
+refresh command as recovery.
+
 The user-local candidate projection has a separate read-only surface. It does
 not need a project checkout and never reads a project glossary.
 

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

@@ -1,8 +1,8 @@
 {
   "schemaVersion": "agentera.generatedBuildSource.v1",
-  "commit": "01a0c460f2310bae5805a637973021af30960ee5",
-  "tree": "998eef2c833de05d61612ce021a02ecb28a0b2b5",
-  "files": 6748,
-  "workingTreeSha256": "3c780bac24a26ed1c40735614d2e9313eb30114901d6b71beb427a74e144bb22",
-  "identitySha256": "04d4e2a388eb6420f37ce0ee4c7052d3a85035d2e0e23e4eaaa980b96e36bf58"
+  "commit": "df1d7a16aa38028099462135eed9f3485e9b2976",
+  "tree": "92881acdddaeb9e0cda57eb37a66ef839437b418",
+  "files": 6815,
+  "workingTreeSha256": "aa5a547104def37dc4cad08cc57312e5b8ed1693db759ca573f436542a4bed77",
+  "identitySha256": "1d8e4406fbd4e18f39e2d32eaf8f9494a78e17a1b225e5d8cd5ba1fd5c652728"
 }

package/bundle/CHANGELOG.md

@@ -18,6 +18,15 @@
 
 ### Changed
 
+- Consented `agentera report refresh --consent local-history` now publishes the
+  deterministic personal-glossary candidate projection for the new evidence
+  generation. Projection failures keep evidence current, return nonzero with
+  separate evidence and projection outcomes, and provide the consented retry command.
+  Refresh ownership now rejects active or unknown owners and safely reclaims a
+  lock only after its recorded process is proven dead. Candidate lists expose
+  privacy-safe fixed-key aggregate candidate and abstention counts, while Profile
+  Full preserves an existing Glossary when mining returns no candidates. Inferred
+  candidates remain review-only and are not automatically admitted.
 - 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
@@ -92,6 +101,11 @@
 
 ### Fixed
 
+- Fixed TODO reconciliation so typed writes use canonical severity headings and
+  insert missing bands before later sections. Duplicate, mismatched, or
+  out-of-order headings now return one bounded actionable diagnosis through
+  TODO reads, Prime, Doctor, and state validation, and block writes before effects.
+  Recognized v2 `## Resolved` headings normalize during entity cutover.
 - Fixed large unsafe inactive TODO status startup to fit its 22,500-byte JSON limit with bounded recovery details.
 - Fixed fresh projects so they can initialize Plan entity state without a legacy upgrade route.
 - Fixed `agentera doctor --format json` to report bounded, read-only retirement
@@ -362,7 +376,7 @@
 - Removed Claude Code as an active runtime, runtime selector, installation target, plugin marketplace, and default analytics source. Historical transcript parsing remains available only with explicit `--import-source claude` consent and inactive provenance.
 - Removed `cursor-agent` as an independent runtime identity. Its binary and corpus source now map to the single `cursor` identity.
 - Removed `rootStatus` from public JSON output (`prime --format json` and `doctor --format json`). The field remains internal for classifier logic but is no longer exposed in diagnostic output.
-- Removed v1 legacy migration paths, standalone skill bundle wording, and obsolete v1 fixture assumptions from the 3.x tree after the 3.0 boundary (`packages/cli/test/cli/v1LegacyCruft.test.ts` guards against reintroduction).
+- Agentera product v1 is unsupported in v3. Product-v1 evidence blocks ordinary commands without mutation and requires a separately previewed and authorized fresh reset. That reset permanently deletes all Agentera state in its listed project, profile, installation, and runtime scopes, retains no backup, and initializes fresh v3 state. The supported one-way v2-to-v3 migration is unchanged, and current schema identifiers ending in `.v1` remain valid.
 - Removed `hej`, `describe`, and `gate` from top-level `agentera --help` and dispatch; unsupported structured requests return runnable corrections to `agentera prime`, `agentera schema`, and `agentera check compact`.
 - Removed the requirement for `uv` or a git checkout on the development channel; `uvx --from git+https://github.com/jgabor/agentera@main agentera` remains the stable 2.x Python line only.
 - Removed `agentera state migrate`, `agentera state backfill`, projection repair, and automatic v1 conversion. Recognized v2 aggregate projects now use `agentera upgrade --dry-run` for preview and full `agentera upgrade --yes` for the one forward mutation path.

package/bundle/UPGRADE.md

@@ -208,11 +208,30 @@ create dual authority, or add a repair or import command.
 
 ## Unsupported legacy state
 
-Pending v1 Markdown, partial, corrupt, and unknown marker-absent state are not
-automatic mutation inputs. `state migrate`, `state backfill`, projection repair,
-v1 conversion, restore, and downgrade are unsupported. Only
-`npx -y agentera@next upgrade --channel development --project "$PWD" --dry-run`
-may inventory cutover input; it cannot publish it.
+Agentera product v1 is unsupported. V3 does not migrate, convert, import, back
+up, restore, or retain v1 state. Current schema identifiers that end in `.v1`
+are not product-v1 evidence and remain supported.
+
+When v3 detects product-v1 evidence, ordinary commands stop without mutation.
+The only continuation is a fresh-v3 reset. Preview the exact bounded project,
+profile, installation, and runtime effects first:
+
+```bash
+npx -y agentera@next upgrade --reset-product-v1 --dry-run --format json
+```
+
+To apply after review, rerun the same scoped command and replace `--dry-run`
+with `--yes --authorization TOKEN`, using the unchanged authorization digest.
+
+This reset is destructive and irreversible. It deletes all Agentera state in
+the listed scopes, retains no backup, and initializes fresh v3 installation
+state. Review `irreversible_loss`, every deletion, and every recreation in the
+preview before applying it. Do not use the reset for v2 projects. Supported v2
+state continues to use the one-way v2-to-v3 preview and apply commands above.
+
+Partial, corrupt, and unknown marker-absent state is not an automatic mutation
+input. `state migrate`, `state backfill`, projection repair, v1 conversion,
+restore, and downgrade are unsupported.
 
 ## Verification and recovery
 

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

@@ -308,8 +308,8 @@
               "sha256": "03fe600a3a27f05daf0d1b59c16b00bedc354a13c70ea60be0b457175fdf743c"
             },
             "reference": {
-              "count": 25,
-              "sha256": "2094946cd6e189c6ab3db16dd0725596cec759abcea88d8335b05215b65ccfc2"
+              "count": 26,
+              "sha256": "aa1ad513d89b66c9133a8572cef2dce760e76d6ee39d2ffa2d4e312578dcc847"
             },
             "state": {
               "count": 38,
@@ -325,8 +325,8 @@
             }
           },
           "total": {
-            "count": 284,
-            "sha256": "3f30b26839aec47639f2197c9efda5caf2a73d5afca9fb38ff9a341e18a72b98"
+            "count": 285,
+            "sha256": "042700a26b34afba57b60eaf4a4529d9e02ce39d8574e6883dfb892eebc64fd5"
           }
         }
       },