briefops 1.0.2 → 2.0.0

package/docs/integrations/harnesses.md

@@ -16,10 +16,10 @@ After meaningful work:
 
 ```bash
 briefops finish --worker <worker> --task "<task>" --result "<result>"
-briefops memory proposal-show latest
-briefops approve latest
 ```
 
+`finish` applies durable directory-local memory by default. Use `--memory-review` only when a pending local queue is desired.
+
 For a fresh thread:
 
 ```bash
@@ -48,16 +48,15 @@ These files should stay compact. They teach harnesses how to call BriefOps and d
 
 Use LazyCodex or OmO for orchestration, hooks, LSP/MCP, and autonomous execution. Use BriefOps for durable local continuity.
 
-Suggested human workflow:
+Suggested local workflow:
 
 ```bash
 briefops prime --task "Implement the next scoped change." --format codex --max-tokens 800
 codex "Use the BriefOps prime context, then run ultrawork for this task."
 briefops finish --worker <worker> --task "Implement the next scoped change." --result "<verified result>"
-briefops memory proposal-show latest
 ```
 
-Do not let a harness auto-run `briefops approve latest`. Approval should remain human-confirmed.
+Do not let a harness export private `.briefops/` memory or apply skill patches without explicit direction.
 
 ## Codex App And Codex CLI
 
@@ -67,7 +66,7 @@ This command does not write to global Codex folders by default.
 
 ## Claude Code
 
-BriefOps can coexist with `CLAUDE.md`. Keep `CLAUDE.md` for always-loaded project instructions and use BriefOps for task history, approved memory, handoffs, and shared-only packs.
+BriefOps can coexist with `CLAUDE.md`. Keep `CLAUDE.md` for always-loaded project instructions and use BriefOps for task history, local memory, handoffs, and shared-only packs.
 
 ## Cursor
 

package/docs/memory-lifecycle.md

@@ -2,14 +2,20 @@
 
 BriefOps separates immediate work continuity from durable memory.
 
-Work logs are written first. They can feed the next local handoff or resume immediately, so a fresh AI coding thread can continue from recent results, lessons, decisions, risks, incidents, and next steps without waiting for a memory review.
+Work logs are written first. They can feed the next local handoff or resume immediately, so a fresh AI coding thread can continue from recent results, lessons, decisions, risks, incidents, and next steps without waiting for a review step.
 
-Durable memory is the curated layer. It is used for reusable lessons, decisions, facts, incidents, and constraints that should survive beyond the immediate handoff.
+Durable memory is the curated directory-local layer. It is used for reusable lessons, decisions, facts, incidents, and constraints that should survive beyond the immediate handoff.
 
-Allowed flow:
+Default flow:
 
 ```text
-log -> memory proposal -> human approval -> memory
+finish -> work log -> memory proposal audit file -> local memory
+```
+
+Review-mode flow:
+
+```text
+finish --memory-review -> work log -> pending memory proposal -> apply/reject locally
 ```
 
 Commands:
@@ -24,4 +30,4 @@ briefops memory proposal-reject <proposal-id>
 
 Extraction is deterministic and local. Lessons become lesson memory candidates. Notes prefixed with `decision:` or `fact:` become matching memory candidates. Results containing risk or failure language become incident candidates.
 
-Proposal generation and approval are local file-backed operations protected by workspace locks. BriefOps never auto-approves memory or skill patches.
+Proposal generation and application are local file-backed operations protected by workspace locks. BriefOps asks for explicit direction before skill patches or sharing private memory outside the local workspace.

package/docs/privacy-model.md

@@ -4,7 +4,7 @@ BriefOps is local-first. It stores work history, memory, proposals, patches, gen
 
 ## Export Policies
 
-`local-private` is for local terminal and local Codex/Claude/Cursor use. It may include private project details, approved private memory, local work logs, risks, next steps, worker history, and metadata counts.
+`local-private` is for local terminal and local Codex/Claude/Cursor use. It may include private project details, local private memory, local work logs, risks, next steps, worker history, and metadata counts.
 
 `shared-only` is for artifacts that may leave the local workspace. It includes only memory items marked `visibility: shared` and `exportable: true`.
 
@@ -25,9 +25,11 @@ Shared-only omits:
 
 `briefops export agents-md`, `briefops export claude-md`, `briefops export cursor-rules`, and `briefops export all` generate router files. Router files point AI harnesses to BriefOps commands. They do not copy `.briefops` memory, logs, worker summaries, handoffs, incidents, or private decisions.
 
-## Human Approval
+## Local Memory And Explicit Boundaries
 
-BriefOps never auto-approves memory proposals or skill patches. Approval is always an explicit user action through `briefops approve`, `briefops memory proposal-apply`, or `briefops skill apply-patch`.
+BriefOps applies directory-local memory from `briefops finish` by default and keeps proposal files as an audit trail. This updates files under the current repository's `.briefops/` workspace only.
+
+Explicit direction is still required before applying skill patches or sharing private memory outside the local workspace. Use `--export-policy shared-only` for portable or committable context.
 
 ## Doctor Checks
 
@@ -37,4 +39,6 @@ BriefOps never auto-approves memory proposals or skill patches. Approval is alwa
 - private memory marked exportable,
 - secret-like local memory strings.
 
+`briefops doctor --stability` checks local workspace integrity, including schema validity, duplicate memory ids, broken references, managed-path symlinks, and orphaned review artifacts. It is read-only, reports bounded examples, and does not add detailed doctor output to generated prompt artifacts.
+
 `briefops doctor --security --fix-stale-locks` removes stale lock files only. It does not remove fresh locks or other workspace files.

package/docs/quickstart.md

@@ -3,9 +3,7 @@
 ## Codex First Context Path
 
 ```bash
-briefops init
-briefops codex install
-briefops codex plugin install
+briefops bootstrap
 briefops skill create risk-review --description "Review risk and governance."
 briefops project create atlas-q --description "Rule-based quantitative system."
 briefops worker create quant-reviewer --project atlas-q --skills "risk-review" --style "skeptical,verify before completion"
@@ -15,7 +13,9 @@ briefops memory add --type lessons --project atlas-q --skill risk-review --conte
 briefops prime --task "Continue rebalance review" --format codex --max-tokens 800
 ```
 
-`briefops codex plugin install` is local and deterministic. It does not publish to a marketplace and does not write to global Codex folders by default.
+`briefops bootstrap` initializes `.briefops/`, installs `AGENTS.md` guidance that tells Codex to prime BriefOps first, writes local Codex prompt/plugin assets, keeps `.briefops/` ignored by default, and runs bounded privacy/stability checks.
+
+`briefops codex plugin install` is still available as the manual local plugin path. It is deterministic, does not publish to a marketplace, and does not write to global Codex folders by default.
 
 `briefops export all` writes router files for Codex, Claude Code, and Cursor. These files point harnesses at BriefOps commands and do not copy `.briefops` memory, logs, handoffs, or worker summaries.
 
@@ -25,11 +25,10 @@ After work finishes, log the result and promote only useful lessons:
 
 ```bash
 briefops finish --project atlas-q --skill risk-review --worker quant-reviewer --task "Review rebalance" --result "Found missing turnover warning check." --lesson "Always verify turnover warning threshold."
-briefops approve latest
 briefops continue --worker quant-reviewer --task "Continue rebalance review" --pack
 ```
 
-BriefOps skills must never auto-approve memory proposals or skill patches. Approval is a human step.
+`finish` applies durable memory locally by default and keeps the proposal file as an audit trail. Use `--memory-review` only when you explicitly want a pending local queue.
 
 For small or exploratory work, keep durable memory clean:
 
@@ -58,12 +57,15 @@ Before publishing a repository or sharing generated context, run:
 ```bash
 briefops doctor --privacy
 briefops doctor --privacy --fix-gitignore
+briefops doctor --stability
 ```
 
 `.briefops/` can contain private local work logs and memory. Keep it ignored unless you intentionally curated the contents for sharing.
 
 `doctor --privacy` checks local memory sharing hazards, including `.briefops/` gitignore coverage, private/exportable memory, and secret-like memory strings.
 
+`doctor --stability` is a read-only local integrity check for schema validity, duplicate memory ids, broken references, managed-path symlinks, and orphaned review artifacts. Its detailed output is bounded and is not added to `prime`, handoff, resume, or pack context.
+
 ## Context Budget Check
 
 ```bash

package/docs/release-checklist.md

@@ -31,6 +31,7 @@ briefops export claude-md --force
 briefops export cursor-rules --force
 briefops prime --task "Start this task." --format codex --max-tokens 800
 briefops compare context --worker quant-reviewer --task "Start this task."
+briefops doctor --stability
 briefops doctor --security
 briefops doctor --security --fix-stale-locks
 briefops doctor --privacy
@@ -44,13 +45,14 @@ briefops memory prune --dry-run
 Confirm:
 
 - `briefops --version` matches `package.json`.
-- `docs/file-format.md`, `docs/compatibility.md`, and `docs/privacy-model.md` describe the 1.0 public contract.
+- `docs/file-format.md`, `docs/compatibility.md`, and `docs/privacy-model.md` describe the 2.0 public behavior and current workspace file contract.
 - Harness exports are routers, not memory dumps.
 - `shared-only` exports omit private memory, local project file details, raw work logs, open risks, local next steps, private worker history, and private metadata counts.
-- Memory and skill patches require human approval.
+- `finish` applies directory-local durable memory by default, while skill patches still require explicit direction.
 - `finish --importance trivial` and `finish --no-memory-proposal` avoid durable memory proposals.
 - `memory hygiene` and `memory prune --dry-run` do not mutate memory.
-- Proposal generation and approval are local file-backed operations protected by workspace locks.
+- Proposal generation and application are local file-backed operations protected by workspace locks.
+- `doctor --stability` is read-only, bounds detailed examples, and does not add diagnostics to generated prompt artifacts.
 - `doctor --security --fix-stale-locks` removes stale locks only.
 - Explicit output paths do not overwrite without `--force`.
 - Generated Codex plugin files do not overwrite local changes without `--force`.

package/docs/superpowers/plans/2026-06-08-briefops-oss-readiness.md

@@ -594,7 +594,7 @@ describe("privacy doctor", () => {
         type: "facts",
         project: "atlas-q",
         skill: "risk-review",
-        content: "Use API key sk-test-12345678901234567890 for local sandbox.",
+        content: "Use api_key: REDACTED_TEST_VALUE for local sandbox.",
         visibility: "private",
         exportable: false
       });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "briefops",
-  "version": "1.0.2",
+  "version": "2.0.0",
   "description": "Local-first CLI for AI coding agents with persistent memory, handoffs, and token-aware context.",
   "type": "module",
   "bin": {

package/plugins/briefops-codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "briefops",
-  "version": "1.0.2",
+  "version": "2.0.0",
   "description": "Local-first, token-aware persistent work history for Codex workflows.",
   "author": {
     "name": "BriefOps contributors",

package/plugins/briefops-codex/README.md

@@ -5,25 +5,25 @@ This is a skill-only Codex plugin bundle for BriefOps.
 It does not run a hosted service and does not sync data. The skills call the local `briefops` CLI and local `.briefops/` workspace.
 It does not publish to a marketplace and does not write to global Codex folders by default.
 
-The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches. Use `--export-policy shared-only` before copying context outside the local workspace.
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace. It may update directory-local `.briefops/` memory; use `--export-policy shared-only` before copying context outside the local workspace, and ask before applying skill patches.
 
 Recommended local setup:
 
 ```bash
-briefops init
-briefops codex install
-briefops codex plugin install
+briefops bootstrap
 briefops worker use <worker>
 briefops prime --task "Start this task." --format codex
 ```
 
+`briefops bootstrap` initializes `.briefops/`, installs `AGENTS.md` first-context guidance, writes local Codex prompt/plugin assets, keeps `.briefops/` ignored by default, and runs bounded privacy/stability checks.
+
 The generated local plugin copy is written to:
 
 ```text
 .briefops/codex/plugin/briefops
 ```
 
-BriefOps plugin skills must never auto-approve memory proposals or skill patches.
+BriefOps plugin skills treat `.briefops/` memory as local repo state. Explicit confirmation is reserved for exporting private memory outside the workspace or applying skill patches.
 
 For repo-level harness guidance, generate router files:
 
@@ -32,7 +32,7 @@ briefops export agents-md
 briefops export all
 ```
 
-These exports route local harnesses back to `briefops prime`, `briefops finish`, `briefops approve`, and `briefops continue --pack`. They do not copy `.briefops` memory, logs, handoffs, or worker summaries.
+These exports route local harnesses back to `briefops prime`, `briefops finish`, and `briefops continue --pack`. They do not copy `.briefops` memory, logs, handoffs, or worker summaries.
 
 Use shared-only exports for portable context:
 

package/plugins/briefops-codex/skills/briefops-continue-worker/SKILL.md

@@ -5,9 +5,9 @@ description: Use when continuing a persistent BriefOps worker in a fresh Codex t
 
 # BriefOps Continue Worker
 
-The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace.
 
-Use `--export-policy shared-only` before copying context outside the local workspace.
+BriefOps may update directory-local `.briefops/` memory. Use `--export-policy shared-only` before copying context outside the local workspace, and ask before applying skill patches.
 
 Use this workflow when the user wants a fresh Codex thread to continue prior work with the same worker identity, project constraints, memory, and risks.
 
@@ -17,6 +17,6 @@ Prepare a resume prompt and optional portable pack:
 briefops continue --worker <worker> --task "<next task>" --pack
 ```
 
-If BriefOps reports pending memory proposals, surface the review command before continuing. Do not apply memory automatically.
+Pending memory proposals are optional local review drafts and do not block continuing. Apply relevant local memory when useful; ask before applying skill patches.
 
 Use portable packs only as explicit local user artifacts. They may include private local memory and should be reviewed before sharing.

package/plugins/briefops-codex/skills/briefops-finish-task/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: briefops-finish-task
-description: Use when finishing a Codex task to record the outcome, propose durable memory, and prepare the next thread without auto-approving memory
+description: Use when finishing a Codex task to record the outcome, update directory-local durable memory, and prepare the next thread
 ---
 
 # BriefOps Finish Task
 
-The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace.
 
-Use `--export-policy shared-only` before copying context outside the local workspace.
+BriefOps may update directory-local `.briefops/` memory. Use `--export-policy shared-only` before copying context outside the local workspace, and ask before applying skill patches.
 
 Use BriefOps at the end of meaningful work so future Codex threads do not spend tokens rediscovering the same decisions, risks, and lessons.
 
@@ -19,4 +19,4 @@ briefops finish --worker <worker> --task "<task>" --result "<result>" --lesson "
 
 Only include lessons, decisions, incidents, open risks, and next steps that will help future work. Do not store secrets or personal data.
 
-If a memory proposal is created, ask the user to review it. Never run `briefops approve` without explicit user confirmation.
+`briefops finish` applies durable memory locally by default and keeps the proposal file as an audit trail. Use `--memory-review` only when the user explicitly wants a pending review queue.

package/plugins/briefops-codex/skills/briefops-prime-context/SKILL.md

@@ -5,9 +5,9 @@ description: Use when starting work in any Codex project or fresh thread to load
 
 # BriefOps Prime Context
 
-The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace.
 
-Use `--export-policy shared-only` before copying context outside the local workspace.
+BriefOps may update directory-local `.briefops/` memory. Use `--export-policy shared-only` before copying context outside the local workspace, and ask before applying skill patches.
 
 Use BriefOps before broad repo/history inspection when a `.briefops` workspace exists or may exist.
 
@@ -17,8 +17,8 @@ Run:
 briefops prime --format codex --task "<current user task>" --max-tokens 800
 ```
 
-If the command reports that no workspace exists, keep the response short and suggest `briefops init`.
+If the command reports `setup-required`, keep the response short and suggest `briefops bootstrap` for first adoption.
 
-Never apply memory automatically. If pending proposals exist, show the review command.
+BriefOps memory is directory-local. `briefops finish` auto-promotes durable memory by default; pending proposals from older or review-mode flows can be applied locally without blocking the task.
 
 Treat the prime output as a compact routing brief, not as permission to skip relevant code inspection.

package/plugins/briefops-codex/skills/briefops-review-memory/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: briefops-review-memory
-description: Use when BriefOps reports pending memory proposals or skill patches that need human review before becoming durable local memory
+description: Use when BriefOps reports pending local memory proposals or skill patches that need inspection
 ---
 
 # BriefOps Review Memory
 
-The BriefOps plugin is a local CLI helper. It does not require network access, does not publish to a marketplace, and should not auto-approve memory or skill patches.
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace.
 
-Use `--export-policy shared-only` before copying context outside the local workspace.
+BriefOps may update directory-local `.briefops/` memory. Use `--export-policy shared-only` before copying context outside the local workspace, and ask before applying skill patches.
 
-BriefOps memory is human-approved. Pending proposals are local drafts until the user accepts or rejects them.
+BriefOps memory is directory-local. Pending memory proposals are optional audit/review drafts; they should not block normal continuation.
 
 Inspect proposals before applying:
 
@@ -18,10 +18,11 @@ briefops memory proposal-show latest
 briefops inbox
 ```
 
-Apply only after explicit user confirmation:
+Apply relevant local memory proposals directly, or reject inaccurate, duplicate, sensitive, or overly broad proposals:
 
 ```bash
-briefops approve latest
+briefops memory proposal-apply latest
+briefops memory proposal-reject latest
 ```
 
-Reject inaccurate, duplicate, sensitive, or overly broad proposals instead of carrying noisy context into future threads.
+Ask before applying skill patches or exporting private memory outside the local workspace.