Jason Woltje
e8058f1e0e
next carries 108 commits main lacks; main carries 23 next lacks, including the MOSAIC_GIT_IDENTITY work that per-agent git credentials depend on. Neither stream alone can ship 0.0.50: next drops identity, main drops everything since the split. Conflicts and how they were settled: - packages/mosaic/package.json test:framework-shell -- union. Neither side removed an entry; next added 6, main added 8, one shared. 50 total. - framework/tools/git/pr-merge.sh -- next's form. It permits base 'main' or 'next'; main's permits 'main' only, and the release line targets next. - framework/tools/git/test-ci-queue-wait-tristate.sh -- both sides appended to the same region (next: merge-readiness assertions; main: a real-clock watchdog control). Kept both. - docs/SITEMAP.md -- both sides appended distinct sections. Kept both.
Documentation Reports
Status: Current evidence index. Reports record reviews, tests, audits, and deferred findings; they are not requirements or operational instructions by themselves.
Use the canonical guide, API contract, source, and tests to determine current behavior. A report retains the scope and verdict of its original review unless a later report explicitly supersedes it.
Documentation evidence
- Documentation catalog and truth audit — migration inventory and static truth assessment.
- Fleet documentation IA closure — active Fleet documentation acceptance evidence; the executable book remains at
docs/fleet/. - Fleet documentation deferrals — explicit holds and deferred live-action boundaries.
- Issue #756 documentation checklist — historical completion checklist for the official Discord plugin workstream.
- Framework consistency audit — 2026-02-17 — historical framework consistency and remediation snapshot.
- Compaction-refresh #830 checklist — historical incomplete-at-snapshot documentation checklist.
Code-review evidence
- Issue #756 independent code review — historical exact-scope review of the official Discord plugin workstream.
- Gateway security-hardening code review — 2026-03-13 — historical no-blocker review snapshot.
Security evidence
- Issue #756 security review — historical security review of Discord ingress, authorization, routing, and residual risks.
QA evidence
- P8-003 performance optimization report — historical implementation evidence; not a current SLO or production benchmark.
- Gateway security-hardening QA report — 2026-03-13 — historical test report with its original live-smoke-test limitation.
Native Kanban/SOT evidence
These reports preserve the review sequence for issue #751. Their GO verdicts apply only to the reviewed historical scope and do not decide current Kanban authority or authorize held KBN-101 database work.
- Initial independent NO-GO — original blocking review.
- Independent re-review GO — follow-up closure review.
- Ultron final GO — historical final-gate record.
- KBN-101 security/architecture review — active review evidence coupled to the held KBN-101 authority surface.
Retention rules
- Preserve report wording and verdicts when migrating historical evidence.
- Keep the reviewed commit, issue, scope, and date visible when present.
- Do not treat an old approval as approval of later code.
- Link each tracked report from this index or an explicitly scoped child index.
- Put current operator procedures in the administrator guide, not in reports.