37 lines
1.7 KiB
Markdown
37 lines
1.7 KiB
Markdown
# 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](documentation/2026-08-10-docs-catalog-audit.md) — migration inventory and static truth assessment.
|
|
- [Issue #756 documentation checklist](documentation/756-discord-plugin-checklist.md) — historical completion checklist for the official Discord plugin workstream.
|
|
|
|
## Code-review evidence
|
|
|
|
- [Issue #756 independent code review](code-review/756-code-review.md) — historical exact-scope review of the official Discord plugin workstream.
|
|
|
|
## Security evidence
|
|
|
|
- [Issue #756 security review](security/756-security-review.md) — historical security review of Discord ingress, authorization, routing, and residual risks.
|
|
|
|
## QA evidence
|
|
|
|
- [P8-003 performance optimization report](qa/p8-003-performance-optimization.md) — historical implementation evidence; not a current SLO or production benchmark.
|
|
|
|
## 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.
|
|
|
|
## Related
|
|
|
|
- [[README|Documentation contract]]
|
|
- [[SITEMAP|Documentation sitemap]]
|
|
- [[archive/README|Documentation archive]]
|