docs: record the audit backlog, replacing the lost tracker database - #14
Merged
Conversation
The 2026-07-25 audit produced 44 tickets in a SQLite tracker under the home directory. That database was destroyed on 2026-07-26 by an unrelated incident that wiped most of ~. The eleven epics survived as GitHub issues #1-#11; the thirty-three sub-tasks existed only in the database. This file is now the source of truth for them. Each entry keeps the file:line citations and the measured numbers from the audit, so nothing has to be rediscovered. It also records the epic -> issue map with each task's tracker uid, recovered from the marker in the issue bodies, so a rebuilt tracker can reuse the same uids and keep the existing issue markers resolving. Includes a "corrections to the audit itself" section: six findings that were wrong on first pass (the BOMs resolve fine; the shaded-jar split is correct; examples-bin is not build output; a mistyped removeEldestEntry does not compile as a silent overload; tasks.uid already existed with deterministic re-keying; ToolExecutorRegistry.register does exist). Recorded so they are not re-filed as defects. Two tickets are already closed and marked as such: AGS-9 (f39e6a1) and AGS-22 (9731fdc). Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2026-07-25 audit produced 44 tickets in a SQLite tracker under the home directory. That database was destroyed on 2026-07-26 by an unrelated incident that wiped most of
~. The eleven epics survived as issues #1–#11; the thirty-three sub-tasks existed only in the database.docs/audit-backlog.mdis now the source of truth for them — committed, so it survives any future machine loss.What it preserves
f39e6a1) and AGS-22 (9731fdc).Corrections to the audit, recorded deliberately
Six findings were wrong on first pass and are documented as such so they are not re-filed as defects:
jagentic-core.-uber), not an anti-pattern.examples-bin/is intentionally tracked scripts, not committed build output.removeEldestEntrydoes not compile as a silent overload — javac rejects the erasure clash, so the compiler guards that bug, not a test.tasks.uidalready existed in the tracker with deterministic re-keying on collision; the real defect was publishing the mutable key in issue markers.ToolExecutorRegistry.register(...)does exist; onlyToolRegistrylacks it.Verification
Docs-only change, no code touched. Rebuilt on a freshly restored toolchain (JDK 21.0.12 + Maven 3.9.16 via sdkman, from a completely empty
~/.m2):jagentic-core95 tests pass, main module rebuild green. CI will confirm on this PR.🤖 Generated with Claude Code