@zonease/aiworker-cli 0.10.3 → 0.11.0

package/README.md

@@ -86,8 +86,12 @@ A single worker can also run without the gateway:
 |                                                                                |
 |  Project Brain (filesystem)        worker.db                                   |
 |  - SOUL / USER / MEMORY            - identity and config                       |
-|  - memories and brain skills       - conversations and messages                |
-|  - policy and capabilities         - encrypted local state                     |
+|  - memories and governance         - conversations and messages                |
+|  - managed native skill            - encrypted local state                     |
+|    projection manifest                                                         |
+|  - native skill files in                                                       |
+|    .agents / .claude                                                           |
+|  - policy and capabilities                                                     |
 |  - admission proposals                                                         |
 |                                                                                |
 |  AIWorker thin adapter                                                         |
@@ -143,7 +147,7 @@ cd ~/code/my-project
 aiworker up --soul developer            # one shot: init + doctor + executor readiness + serve
 ```
 
-`aiworker up` lays down the Project Brain layout under `<cwd>/.aiworker/` (worker.db, master key, persona, brain skills), runs the preflight checks, reports executor readiness, and starts the worker HTTP/admin server (default `:9217`). It does not choose an executor for you; use `aiworker executor select --engine <id> --apply` for that. Pick a Soul from `developer` / `hr-recruiting` / `finance-ops` / `qa-reviewer` / `general-assistant` — Souls shape persona / risk preferences / default brief sections; governance kernel behavior is the same across all Souls.
+`aiworker up` lays down the Project Brain layout under `<cwd>/.aiworker/` (worker.db, master key, persona, policy, memories, native skill projection manifest) and projects managed `aiworker-*` executor-native skills under `.agents/skills` and `.claude/skills`. It then runs preflight checks, reports executor readiness, and starts the worker HTTP/admin server (default `:9217`). It does not choose an executor for you; use `aiworker executor select --engine <id> --apply` for that. Pick a Soul from `developer` / `hr-recruiting` / `finance-ops` / `qa-reviewer` / `general-assistant` — Souls shape persona / risk preferences / default brief sections; governance kernel behavior is the same across all Souls.
 
 Step-by-step alternative:
 
@@ -172,6 +176,42 @@ Full CLI reference: [`docs/cli.md`](docs/cli.md).
 
 ---
 
+## Developer repo proof loop
+
+For a repo-scoped developer worker, AIWorker adds a reviewable proof loop around
+the executor:
+
+1. The external executor still performs the work.
+2. Brain Journal records task intent, selected context, executor events, tool
+   signals, authority preflight, Gate verdict, and outcome.
+3. Brain Gate separates hard invariants from Brain Engine review and heuristic
+   quality signals.
+4. Failed or incomplete work can be held or rerun with parent/child lineage.
+5. Useful lessons become Brain Inbox candidates first; canonical memory writes
+   still go through admission approval and apply.
+
+Useful local commands:
+
+```sh
+aiworker run --message "review this change"
+aiworker brain journal show <taskId>
+aiworker brain inbox propose <taskId>
+```
+
+When running the worker HTTP API, operator-triggered reruns are available at:
+
+```sh
+curl -X POST \
+  -H "Authorization: Bearer $(cat .aiworker/local/bootstrap-token.txt)" \
+  http://127.0.0.1:9217/api/worker/orchestrator/tasks/<taskId>/rerun
+```
+
+Authority preflight is a truthfulness surface, not a sandbox claim. High-risk
+ambient executor work is marked as observe-only unless the capability is
+explicitly brokered by AIWorker.
+
+---
+
 ## Start a fleet (multiple workers + gateway)
 
 The gateway aggregates multiple workers into a fleet: one operator CLI controls all of them, while each worker keeps owning its own brain, conversations, and secrets.
@@ -352,7 +392,7 @@ and [`docs/changelog.md`](docs/changelog.md).
 > section in [`docs/governance-node-status.md`](docs/governance-node-status.md).
 > Before 1.0.0, CLI / API / config shapes may still change.
 
-CLI npm latest: **0.10.3**.
+CLI npm latest: **0.11.0**.
 
 | Module | Status |
 |---|---|