feat: add operator report closeout

Author: solomonneas

CHANGELOG.md

@@ -84,7 +84,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `brigade learn plan/doctor/import-issues` for bounded local learning candidates that become reviewed tasks, handoffs, suppressions, accepted risk, archive, or dismissal.
 - `brigade tools pack build/list/show/archive` and `brigade tools sync plan/apply` for portable tool evidence bundles and reviewed projection sync over the existing managed projection path.
 - `brigade work backup closeout`, `brigade security closeout`, `brigade handoff closeout`, `brigade memory care closeout`, and `brigade work acceptance` for reviewable local closeout and acceptance rollup receipts.
-- `brigade center status/activity/reviews/templates` and `brigade center report plan/build/list/show/archive` for read-only local operator-center summaries and local report bundles over work, scanner, review, handoff, tool, learning, context, project, security, and release state.
+- `brigade center status/activity/reviews/templates` and `brigade center report plan/build/list/show/archive/review/compare/closeout` for read-only local operator-center summaries, local report bundles, daily action plans, freshness comparison, and reviewed report closeout over work, scanner, review, handoff, tool, learning, context, project, security, and release state.
 - `brigade roadmap audit` and `brigade roadmap patterns` for roadmap closure checks, stale phase warnings, documented command drift, neutral pattern-family coverage, and source-pattern decisions.
 - `brigade repos init/list/show/scan/doctor/import-issues` for gitignored local repo-fleet readiness checks, safe setup metadata, fallback guidance detection, and `repo-fleet` work inbox imports.
 - `brigade work sweep closeout <sweep-id|latest>` for reviewable sweep closeout records that block unresolved pending imports, support explicit deferrals, and surface unclosed sweeps through inbox hygiene.

README.md

@@ -327,6 +327,9 @@ brigade center report build
 brigade center report list
 brigade center report show <report-id>
 brigade center report archive <report-id>
+brigade center report review <report-id>
+brigade center report compare <report-id>
+brigade center report closeout <report-id>
 brigade work run
 brigade work run --queue-next
 brigade work run "review today's changes"

ROADMAP.md

@@ -48,7 +48,7 @@ Goal: make Brigade a safe target for local automations that discover useful work
 - Audit roadmap closure and neutral pattern coverage. Status: started with `brigade roadmap audit`, `brigade roadmap patterns`, stale phase warnings, documented command drift checks, roadmap-audit imports, and source-pattern decision records without public reference names.
 - Inspect local repo fleet readiness without copying private repo contents. Status: started with gitignored `.brigade/repos.toml`, `brigade repos init/list/show/scan/doctor/import-issues`, safe metadata summaries, AGENTS and fallback guidance detection, repo-fleet imports, and daily-loop health surfacing.
 - Close out scanner sweeps after review. Status: started with `brigade work sweep closeout <sweep-id|latest>`, deferred import recording, missing-reference blocking, and inbox hygiene warnings for unclosed sweeps.
-- Inspect local operator state from one read-only center view. Status: started with `brigade center status/activity/reviews/templates` and `brigade center report plan/build/list/show/archive`, aggregating local work, imports, sweeps, reviews, handoffs, tools, learning, context packs, projects, security, and release state into JSON and local report bundles without a daemon or server.
+- Inspect local operator state from one read-only center view. Status: started with `brigade center status/activity/reviews/templates` and `brigade center report plan/build/list/show/archive/review/compare/closeout`, aggregating local work, imports, sweeps, reviews, handoffs, tools, learning, context packs, projects, security, and release state into JSON, action plans, closeouts, and local report bundles without a daemon or server.
 
 ## Later Phase: Chat Surface Scanners
 

docs/operator-center.md

@@ -18,6 +18,9 @@ brigade center report build
 brigade center report list
 brigade center report show <report-id>
 brigade center report archive <report-id>
+brigade center report review <report-id>
+brigade center report compare <report-id>
+brigade center report closeout <report-id>
 ```
 
 `status` summarizes active work, pending tasks, pending imports, scanner sweep health, review health, handoff drafts, tool catalog health, learning candidates, context packs, release readiness, release candidates, repo fleet, roadmap health, project consolidation, and security health.
@@ -51,6 +54,22 @@ Each bundle contains:
 - `OPERATOR_REPORT.html`, a dependency-free escaped static rendering of the Markdown report.
 - `CENTER_EVIDENCE.json`, stable JSON evidence for wrappers.
 
-`brigade center report plan` previews the same evidence without writing. `list`, `show`, and `archive` inspect or move local bundles. Report health warns when the latest bundle is stale, references missing receipts, was built from an older git HEAD, or newer center activity exists. `brigade work brief`, `brigade work doctor`, `brigade release doctor`, and release candidate evidence surface those report health checks.
+`brigade center report plan` previews the same evidence without writing. `list`, `show`, and `archive` inspect or move local bundles. Report health warns when the latest bundle is unclosed, stale, references missing receipts, was built from an older git HEAD, or newer center activity exists. `brigade work brief`, `brigade work doctor`, `brigade release doctor`, release candidate evidence, and release candidate compare surface those report health checks.
+
+`brigade center report review <report-id|latest>` groups actionable report items into:
+
+- urgent blockers
+- pending work imports
+- code review findings
+- handoff drafts
+- scanner sweep issues
+- tool approvals, checkpoints, and runs
+- backup, security, and memory-care issues
+- release readiness and candidate issues
+- project and learning candidates
+
+`brigade center report compare <report-id|latest>` checks the report against current local state. It warns when HEAD changed, referenced receipts are missing, newer activity exists, newer release/readiness/verification/review/sweep/security receipts exist, or the review queue changed.
+
+`brigade center report closeout <report-id|latest>` writes `CLOSEOUT.json` in the report bundle. Closeout states are `reviewed`, `deferred`, `superseded`, and `archived`. Closeout stores a reviewed timestamp, reason, unresolved item count, deferred item ids, and report fingerprint.
 
 The operator center never invokes scanners, tools, reviewers, handoff ingestion, release publishing, git commands that mutate state, or remote APIs. Only `center report build` and `center report archive` write local gitignored report bundle files.

docs/release-candidates.md

@@ -22,7 +22,7 @@ brigade release candidate archive <candidate-id>
 .brigade/release/candidates/
 ```
 
-`list` and `show` inspect bundles. `compare` checks the candidate against current local state, including changed HEAD, missing referenced receipts, newer verification or review evidence, newer scanner or security evidence, and docs changed after the bundle was built.
+`list` and `show` inspect bundles. `compare` checks the candidate against current local state, including changed HEAD, missing referenced receipts, newer verification or review evidence, newer scanner, security, or operator report evidence, and docs changed after the bundle was built.
 
 `closeout` writes a local `CLOSEOUT.json` into the candidate bundle with `draft`, `reviewed`, `superseded`, or `archived` state. `archive` moves a reviewed candidate into the local archive so it no longer appears as the latest candidate.
 
@@ -42,7 +42,7 @@ Each candidate contains:
 
 These are warnings because candidate bundles are review artifacts. They do not replace release readiness checks, verification, code review closeout, or content guard.
 
-Release readiness and candidate bundles include operator report health so an operator can tell whether the local daily review packet is fresh before publishing manually.
+Release readiness, candidate bundles, and candidate compare include operator report health so an operator can tell whether the local daily review packet is fresh and closed out before publishing manually.
 
 ## Boundary
 

docs/roadmap-completion-plan.md

@@ -567,7 +567,7 @@ Implementation scope:
 - Add `brigade center activity`.
 - Add `brigade center reviews`.
 - Add `brigade center templates`.
-- Add `brigade center report plan/build/list/show/archive`.
+- Add `brigade center report plan/build/list/show/archive/review/compare/closeout`.
 - Aggregate existing local state only: work sessions, pending tasks, pending imports, scanner runs and sweeps, review runs, handoff drafts, tool approvals, checkpoints, context packs, learning candidates, repo fleet, project decisions, security health, release readiness, and release candidates.
 - Every center item includes subsystem, local id, status, safe summary, suggested next command, and priority or severity when available.
 - Keep center commands read-only and JSON-first for future wrappers.
@@ -576,7 +576,7 @@ Implementation scope:
 Acceptance:
 
 - Tests cover center status, activity, reviews, and templates in text and JSON.
-- Tests cover center report plan, build, list, show, archive, freshness checks, and release/work integration.
+- Tests cover center report plan, build, list, show, archive, review, compare, closeout, freshness checks, and release/work integration.
 - Tests prove center commands are read-only.
 - Public docs describe the operator center as local CLI output, not a hosted dashboard, app server, daemon, or sync engine.
 
@@ -588,9 +588,16 @@ Phase 36 status:
 Phase 37 status:
 
 - Implemented command surface: `brigade center report plan/build/list/show/archive`.
-- Operator reports write `OPERATOR_REPORT.md`, `OPERATOR_REPORT.html`, and `CENTER_EVIDENCE.json` under `.brigade/center/reports/`.
+- Operator reports write `OPERATOR_REPORT.md`, `OPERATOR_REPORT.html`, `CENTER_EVIDENCE.json`, and optional `CLOSEOUT.json` under `.brigade/center/reports/`.
 - Work brief, work doctor, release doctor, and release candidate evidence include operator report freshness.
 
+Phase 38 status:
+
+- Implemented command surface: `brigade center report review/compare/closeout`.
+- Report review groups pending items into an action plan with suggested commands.
+- Report compare checks changed HEAD, missing receipts, newer local activity, newer subsystem receipts, and changed review queues.
+- Report closeout stores reviewed, deferred, superseded, or archived metadata without taking actions on queued items.
+
 ## Suggested Execution Order
 
 1. Roadmap audit, inspiration pattern registry, and repo-fleet readiness.