agentera 3.0.0-dev.8 → 3.0.0-dev.81

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,43 +1,273 @@
-# Agentera CLI (npm)
+# Agentera CLI
 
-Native TypeScript CLI for Agentera 3.x, published as [`agentera`](https://www.npmjs.com/package/agentera).
+Native TypeScript CLI for Agentera 3.0, published as
+[`agentera`](https://www.npmjs.com/package/agentera). The npm package is
+self-contained: compiled commands live in `dist/`; the canonical shared skill,
+its schemas, required references, and `registry.json` live in `bundle/`. It
+ships no host-native plugin, hook, command, agent, descriptor, or marketplace
+surface.
 
-| Dist tag | Channel | Use for |
-| --- | --- | --- |
-| `@latest` | stable (2.x) | Supported production line |
-| `@next` | development (3.x pre-releases) | Early testing of the self-contained npm CLI |
+Until the stable dist-tag is promoted, run 3.0 through `@next`:
 
-## Quick start
+```bash
+npx -y agentera@next prime --context status --format json
+npx -y agentera@next doctor --format json
+```
+
+The first command is the one-call pre-cutover bootstrap. Clean, v2, and
+partially migrated projects return bounded `blocked` output with the exact full
+entity-upgrade command in `state_cutover.recovery_command`; v3 returns `ok`
+unless health state makes it `degraded`. Every recovery command remains on
+`@next`, and an `ok` outcome needs no fallback or second dashboard call. Served
+capability instructions and bundled startup schemas use that same exact
+development-channel executable. Package verification parses every registry-owned
+instructional Markdown, YAML, and JSON surface, rejects duplicate keys and
+unsafe aliases, reason-classifies non-guidance and generated declarations, and
+closes every static constructor importer and re-exporter through conservative
+TypeScript module closure. Every closure module is an explicit producer or
+reasoned non-producer. Generated declaration fields and source/package records
+must match exactly, and unused exemptions fail. Only the
+adjacent ordered stable-v2 preview/apply pair in `UPGRADE.md` may execute
+`@latest`. The second command is an independent read-only evidence probe on the
+same channel.
+
+`prime --format json` returns a bounded decision brief (at most 12000 UTF-8
+bytes). Status startup returns
+`capability_context.instructions` and bounded
+`capability_context.context.status_context` together (at most 25000 UTF-8
+bytes). Omitted detail names its authoritative recovery command. `doctor`
+returns detailed read-only evidence and exact user actions. Entity-mode projects
+with an absent or unsafe TODO reconciliation marker return `action_required`
+instead of `ok` or `up_to_date`. A safe inactive project reports an activation
+preview and its exact effect-bound apply command:
+
+```bash
+npx -y agentera@next state todo activate --dry-run --format json
+npx -y agentera@next state todo activate --effect-sha256 EFFECT_SHA256 --yes --format json
+```
+
+An unsafe active project with an existing marker reports the separate repair
+preview and effect-bound apply path:
+
+```bash
+npx -y agentera@next state todo repair --dry-run --format json
+npx -y agentera@next state todo repair --effect-sha256 EFFECT_SHA256 --yes --format json
+```
+
+Unsafe inactive evidence (unmatched projections, duplicate public work, stale
+entity status, or prospective resurrection) reports a bounded, content-private
+diagnosis and an owner-correction preview. Supply a complete `id` and
+one-based `source_line` mapping for every managed row, then confirm the exact
+effect-bound apply command. The correction preserves Markdown-owned public
+state and Agentera-owned operational fields without an intermediate activation.
+`check validate state` reports the same read-only diagnosis. Healthy active TODO projections keep the existing output.
+
+## Shared-skill integration
+
+Agentera uses one portable integration: the Agentera CLI plus the shared skill
+at `~/.agents/skills/agentera`. Normal upgrade previews and applies app/project
+migration only. It has no current-runtime selector and does not create native
+runtime resources.
+
+```bash
+npx -y agentera@next upgrade --channel development --project "$PWD" --dry-run
+npx -y agentera@next upgrade --channel development --project "$PWD" --yes
+```
+
+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
+npx -y agentera@next upgrade --legacy-cleanup claude.agentera-skill-link --dry-run
+```
+
+It selects declared native Agentera resources only. Each removal needs a
+matching whole-resource ledger identity and fingerprint; shared Codex config
+keys require unavailable key-level evidence and remain action-required.
+Historical transcript import is also explicit (`agentera report refresh
+--import-source claude`) and is excluded from default active-runtime analytics.
+
+## Bounded state retrieval
+
+The executable contract is
+[`references/artifacts/state-storage-authority.yaml`](../../references/artifacts/state-storage-authority.yaml)
+and is projected by `agentera schema --format json`.
+
+```bash
+agentera state plan list --format json
+agentera state plan get --id PLAN_ID --format json
+agentera state plan tasks list --limit 20 --format json
+agentera state experiments list --objective OBJECTIVE_ID --format json
+agentera state experiments get --id EXPERIMENT_ID --format json
+```
+
+Pages use opaque snapshot cursors, explicit omission fields, whole-entry output
+bounds, and exact retrieval. Plan history is owned by active/archive plan files;
+plan task retrieval is active-only. Experiment history is objective-scoped and
+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
+
+An explicitly consented refresh is the production candidate producer:
 
 ```bash
-npx -y agentera@next prime --format json
-npx -y agentera@next upgrade --dry-run --channel development
+npx -y agentera@next report refresh --consent local-history
 ```
 
-Run those from a project root. `prime` reports `project_integration.recommendation`
-(`stay` or `upgrade`) and suggested commands for the current repo.
+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.
 
-Full preview instructions, channels, and migration paths: [`UPGRADE.md`](../../UPGRADE.md).
+The user-local candidate projection has a separate read-only surface. It does
+not need a project checkout and never reads a project glossary.
 
-## Editor runtime installs
+```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
+```
 
-Agentera ships a skill bundle for supported editor runtimes (Claude Code, OpenCode, Cursor, Copilot CLI, Codex CLI). Install steps and parity details live in the [repository README — Internals](../../README.md#internals) and [`references/adapters/runtime-feature-parity.md`](../../references/adapters/runtime-feature-parity.md).
+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.
 
-## Package layout
+## Personal glossary decisions
 
-- `dist/` — compiled CLI (`agentera` bin)
-- `bundle/` — shipped app data (`skills/`, `references/`, `registry.json`)
+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
+```
 
-Requires Node.js 22+.
+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
 
-Build and test from the monorepo:
+Requires Node.js 22+ and pnpm 10.30.3.
+
+### Generated-output ownership and recovery
+
+The canonical producer, reader, packing, retention, and recovery contract is
+[v3 npm packaging and verification](../../docs/packaging/v3-packaging.md).
+Generated generations are disposable; source files and the package registry
+remain authoritative. Use its recovery matrix rather than deleting uncertain
+state.
 
 ```bash
-pnpm -C packages/cli build
 pnpm -C packages/cli test
-pnpm -C packages/cli run publish:dev   # publishes with @next tag
+pnpm -C packages/cli run verify:package
+pnpm -C packages/cli run typecheck
+pnpm -C packages/cli build
+pnpm -C packages/cli run verify:generated-overlap
+pnpm -C packages/cli run generated:cleanup -- --dry-run --json
+pnpm -C packages/cli run lint
 ```
 
-See [`AGENTS.md`](../../AGENTS.md) for capability validation and commit conventions.
+Use `pnpm -C packages/cli run pack:dry-run` to inspect the exact isolated
+publication surface. Do not publish from a normal development or capability
+cycle.

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

@@ -0,0 +1,8 @@
+{
+  "schemaVersion": "agentera.generatedBuildSource.v1",
+  "commit": "3780e6727365095a4cf8cd265a9646fba4570593",
+  "tree": "ccb81233f9d1c79aa0b642d3b93771011a09ea89",
+  "files": 6908,
+  "workingTreeSha256": "16fc45b5e88a8ced49f2b84624a58dd63ccb85ebd34939260abc3b012a07b95e",
+  "identitySha256": "0857864ae6ee7d83e931d5049cb5386a1de05e04694fd9b28f400990bda9d147"
+}