Single follow-up to the merged audit (PR #66): record where the open work now lives.
- `omp-docs/reports/index.md` gains a tracking line listing the vulnerability issues
[dank/command-center#67](https://gitea.franksdank.cloud/dank/command-center/issues/67)–[#77](https://gitea.franksdank.cloud/dank/command-center/issues/77),
one per host-and-package cluster.
- `omp-docs/log.md`: the 2026-10-21 entry now names the merged PR and the issue range.
Checks: `scripts/kb-lint.sh omp-docs` → `0 violation(s)`; `scripts/kb-coverage.py omp-docs` → `0 issue(s)`.
---
cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05
The audit's vulnerability clusters are now filed on Gitea as
dank/command-center#67..#77, one issue per host-and-package cluster. Link
them from omp-docs/reports/index.md and record the PR/issue references on
the matching log.md entry, so a reader of the audit can find the open work
without leaving the bundle.
dank
merged commit abee84ddad into main2026-10-27 19:57:11 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Single follow-up to the merged audit (PR #66): record where the open work now lives.
omp-docs/reports/index.mdgains a tracking line listing the vulnerability issuesdank/command-center#67–#77,
one per host-and-package cluster.
omp-docs/log.md: the 2026-10-21 entry now names the merged PR and the issue range.Checks:
scripts/kb-lint.sh omp-docs→0 violation(s);scripts/kb-coverage.py omp-docs→0 issue(s).cwd: /home/blank/.omp/wt/wt-20261019-125509-7c8a99d · session: 01a155bb-6474-7366-be9d-629f74af0e05