briefops 2.0.0 → 2.1.1

package/docs/release-checklist.md

@@ -10,6 +10,7 @@ npm pack --dry-run
 npm run verify:release
 briefops --help
 npm whoami
+npm view briefops versions --json
 ```
 
 `npm audit --audit-level=moderate` is included in `npm run verify:release`. It contacts the npm registry and sends dependency/audit metadata, so run it only from an environment where that network disclosure is acceptable.
@@ -31,12 +32,17 @@ 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 obs continuity --worker quant-reviewer --task "Start this task." --json
 briefops doctor --stability
 briefops doctor --security
 briefops doctor --security --fix-stale-locks
 briefops doctor --privacy
+briefops doctor --strict --json
+briefops harness route --task "Review work"
+briefops harness matrix
 briefops finish --worker quant-reviewer --project atlas-q --skill risk-review --task "Review work" --result "Found unresolved risk." --lesson "Check unresolved risk before finishing." --importance durable
-briefops approve latest
+briefops finish --worker quant-reviewer --project atlas-q --skill risk-review --task "Review pending memory path" --result "Created review proposal." --decision "Use review mode only when a pending queue is explicitly desired." --memory-review
+briefops memory proposal-apply latest
 briefops finish --worker quant-reviewer --task "Fix typo" --result "Fixed typo." --importance trivial
 briefops memory hygiene
 briefops memory prune --dry-run
@@ -45,15 +51,21 @@ 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 2.0 public behavior and current workspace file contract.
+- `docs/file-format.md`, `docs/compatibility.md`, and `docs/privacy-model.md` describe the 2.1.x public behavior and current workspace file contract.
+- The target package version is not already present in `npm view briefops versions --json`.
+- npm authentication has read-write access to the `briefops` package.
+- `briefops harness route` returns the workflow depth, artifacts, exit criteria, and final-response contract for the task.
+- `briefops obs continuity` reports compression, continuity, queues, and memory hygiene counts without dumping private memory.
 - 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.
 - `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.
+- Memory items and proposals can carry optional evidence anchors without breaking older memory files.
 - 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.
+- `doctor --strict --json` reports `releaseReady: false` when any release-readiness warning or failure remains.
 - Explicit output paths do not overwrite without `--force`.
 - Generated Codex plugin files do not overwrite local changes without `--force`.
 - `.briefops/` is ignored or intentionally curated.
@@ -66,5 +78,7 @@ git status --short --branch
 git tag v<version>
 git push origin HEAD
 git push origin v<version>
+npm view briefops versions --json
 npm publish
+npm view briefops version
 ```

package/docs/roadmap.md

@@ -8,15 +8,22 @@
 - shared-only export privacy hardening
 - file format, compatibility, and privacy model documentation
 
-## Near Term After 1.0
+## 2.1.x Complete
 
-- expand context savings eval fixtures
-- improve memory hygiene suggestions beyond dry-run reporting, without auto-pruning
-- release readiness CI
+- strict local release-readiness checks that aggregate stability, security, privacy, and memory hygiene
+- evidence-backed memory references for decisions, lessons, incidents, and risks
+- continuity observability reports for context compression, queues, and hygiene signals
+- Codex-first Master Harness routing for task workflow depth
+- npm package refresh for the 2.1.x public release line
+
+## Near Term After 2.1.x
+
+- persistent `.briefops/harness/` route, goal, finding, and verification ledgers
+- stronger Spec-Kit detection and route-aware handoff
+- richer eval fixtures for context savings and continuity quality
 
 ## Later
 
-- optional cross-harness projection beyond router files
 - richer eval fixtures for token savings
 - curated shared-memory export bundles
 - signed release artifacts

package/docs/token-budget.md

@@ -50,6 +50,14 @@ briefops compare context --worker <worker> --task "Review this PR."
 
 The command estimates local `.briefops` candidate inputs such as project context, worker summary, active memory, and recent logs, then compares them with compiled `briefops prime` output.
 
+Use `obs continuity` when you want the same context compression signal alongside continuity health, local queue counts, and memory hygiene:
+
+```bash
+briefops obs continuity --worker <worker> --task "Review this PR." --json
+```
+
+This command is read-only and reports counts and token estimates rather than dumping private memory.
+
 ## Harness Router Budgets
 
 Harness exports should stay small:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "briefops",
-  "version": "2.0.0",
+  "version": "2.1.1",
   "description": "Local-first CLI for AI coding agents with persistent memory, handoffs, and token-aware context.",
   "type": "module",
   "bin": {
@@ -44,7 +44,7 @@
     "zod": "^3.23.8"
   },
   "devDependencies": {
-    "@types/node": "^22.5.5",
+    "@types/node": "^26.0.0",
     "tsx": "^4.19.1",
     "typescript": "^5.6.2",
     "vitest": "^4.1.8"

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

@@ -1,6 +1,6 @@
 {
   "name": "briefops",
-  "version": "2.0.0",
+  "version": "2.1.1",
   "description": "Local-first, token-aware persistent work history for Codex workflows.",
   "author": {
     "name": "BriefOps contributors",
@@ -29,6 +29,7 @@
       "Write"
     ],
     "defaultPrompt": [
+      "Route this task through the BriefOps Master Harness.",
       "Start this task with the smallest useful BriefOps context.",
       "Finish this task and prepare memory for the next thread."
     ],

package/plugins/briefops-codex/README.md

@@ -25,6 +25,8 @@ The generated local plugin copy is written to:
 
 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.
 
+Use `briefops-route-task` at the start of development work when Codex should classify the task before implementation. It routes small fixes, features, refactors, UI work, incidents, research, code review, and release preparation to the smallest sufficient workflow depth.
+
 For repo-level harness guidance, generate router files:
 
 ```bash

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

@@ -0,0 +1,33 @@
+---
+name: briefops-route-task
+description: Use when starting Codex development work to classify the task and choose the smallest sufficient BriefOps Master Harness workflow
+---
+
+# BriefOps Route Task
+
+The BriefOps plugin is a local CLI helper. It does not require network access and does not publish to a marketplace.
+
+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 before implementation when the task may need memory, specification, planning, findings, verification, or handoff discipline.
+
+Run:
+
+```bash
+briefops harness route --task "<current user task>"
+```
+
+For explicit routing, pass a task type:
+
+```bash
+briefops harness route --task "<current user task>" --type large-feature
+```
+
+Use the route as a workflow contract:
+
+- Do not force full specification on tiny tasks.
+- Do not skip goal ledgers, findings, visual evidence, or handoff when the route requires them.
+- If repository evidence contradicts the inferred route, choose the safer route and say why.
+- Treat `briefops prime` as the memory intake step and `briefops finish` as the work-log/memory closeout step.
+
+Supported task types: small-bug-fix, medium-feature, large-feature, refactor, dependency-upgrade, ui-change, test-repair, production-incident, documentation-task, architecture-decision, exploratory-research, code-review, release-preparation.