feat: add local operator reports

Author: solomonneas

.gitignore

@@ -82,6 +82,7 @@ memory/20[0-9][0-9]-[0-1][0-9]-[0-3][0-9].md
 memory/handoff-inbox/
 
 # brigade local state (logs, scrub cache, dogfood runs, work sessions).
+.brigade/center/
 .brigade/dogfood.toml
 .brigade/logs/
 .brigade/runs/

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` for read-only local operator-center summaries 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` 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 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

@@ -322,6 +322,11 @@ brigade center status
 brigade center activity
 brigade center reviews
 brigade center templates
+brigade center report plan
+brigade center report build
+brigade center report list
+brigade center report show <report-id>
+brigade center report archive <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`, aggregating local work, imports, sweeps, reviews, handoffs, tools, learning, context packs, projects, security, and release state 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`, 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.
 
 ## Later Phase: Chat Surface Scanners
 

docs/operator-center.md

@@ -13,6 +13,11 @@ brigade center reviews
 brigade center reviews --json
 brigade center templates
 brigade center templates --json
+brigade center report plan
+brigade center report build
+brigade center report list
+brigade center report show <report-id>
+brigade center report archive <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.
@@ -30,4 +35,22 @@ brigade center templates --json
 
 `templates` lists local workflow templates for context packs, tool packs, project audits, release candidates, and review closeouts.
 
-The operator center never invokes scanners, tools, reviewers, handoff ingestion, release publishing, git commands that mutate state, or remote APIs. It only reads existing local files and prints text or JSON.
+Every center row uses the same wrapper-facing fields: `subsystem`, `local_id`, `status`, `priority`, `severity`, `safe_summary`, `created_at`, `updated_at`, `receipt_path`, `path`, and `suggested_next_command`.
+
+## Operator Reports
+
+`brigade center report build` writes a local bundle under:
+
+```text
+.brigade/center/reports/
+```
+
+Each bundle contains:
+
+- `OPERATOR_REPORT.md`, a daily review summary with review queue, activity, and suggested next commands.
+- `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.
+
+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

@@ -34,13 +34,16 @@ Each candidate contains:
 - `RELEASE_NOTES_DRAFT.md`, an editable draft inferred from `CHANGELOG.md`, commit subjects since the base ref, and touched docs. Uncertain sections are marked `review-needed`.
 - `PUBLISH_PLAN.md`, a manual checklist for verification, closeout, release doctor, content guard, tag, push, and release creation. Remote-mutating commands are marked manual-only and are not run.
 - `EVIDENCE.json`, stable wrapper-friendly evidence for the release readiness receipt, work closeout, verification receipt, code review closeout, scanner sweep state, security state, handoff state, git state, changed files, docs touch status, content-guard summaries, blockers, warnings, and suggested next commands.
+- latest operator report health, including stale reports, missing receipt references, changed HEAD, and newer center activity warnings.
 
 ## Candidate Health
 
 `brigade release doctor` warns when the latest candidate is stale, references missing receipts, was built from blocked readiness, or no longer matches the current git HEAD.
 
 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.
+
 ## Boundary
 
 Release candidate commands are local and explicit. Brigade does not push, tag, create GitHub releases, mutate pull requests, edit changelogs outside the candidate bundle, upload artifacts, approve content-guard findings, start daemons, install schedulers, or store secrets.

docs/release-readiness.md

@@ -46,7 +46,7 @@ Release readiness includes:
 - latest security health and evidence state
 - handoff draft and ingest health
 - local closeout state for backup, handoff, memory-care, security, and release candidates when available
-- context pack freshness, project consolidation state, learning candidates, and operator-center pending review summaries where configured
+- context pack freshness, project consolidation state, learning candidates, operator-center pending review summaries, and operator report freshness where configured
 - git branch, dirty tracked files, upstream, ahead count, and behind count
 - README, CHANGELOG, and ROADMAP touch warnings when user-facing code changed
 - content-guard tip scan when available

docs/roadmap-completion-plan.md

@@ -567,13 +567,16 @@ Implementation scope:
 - Add `brigade center activity`.
 - Add `brigade center reviews`.
 - Add `brigade center templates`.
+- Add `brigade center report plan/build/list/show/archive`.
 - 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.
+- Build local report bundles only under `.brigade/center/reports/`, with Markdown, dependency-free HTML, and JSON evidence.
 
 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 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.
 
@@ -582,6 +585,12 @@ Phase 36 status:
 - Implemented command surface: `brigade center status/activity/reviews/templates`.
 - Center status aggregates local subsystem health. Center activity reads receipts and pack metadata. Center reviews presents one pending review queue across imports, learning, projects, and context health. Center templates lists local workflow templates for wrappers.
 
+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/`.
+- Work brief, work doctor, release doctor, and release candidate evidence include operator report freshness.
+
 ## Suggested Execution Order
 
 1. Roadmap audit, inspiration pattern registry, and repo-fleet readiness.