Rongsong Shen
d26ff8870d
The buglog was one 27K-line JSON file whose fields covered only symptom,
root cause and fix, as free text: 2% of entries named the code version a
bug was found on, 12% the build profile, 36% a way to reproduce, and 58% of
the file was OpenWolf hook auto-detections ("Missing guard clause",
"Function not marked async" on .md files).
- .claude/skills/buglog/bug-record.md: the record standard. Eight
sections (Summary as the title, Description, Environment, Reproduction;
Root cause, Fix, Verification, References once fixed), each with the
content it must contain -- e.g. Environment needs the OS, the libc the
failing binary loads (from its ELF interpreter: glibc 2.42 in the nix
shell vs 2.40 on the host), toolchain, build profile and commit.
- .wolf/bugs/<id>.md: 500 records migrated from buglog.json; every field
verified to round-trip. They carry legacy: true and an explicit "not
recorded" where the old log had no such field; component derived from
file paths, severity from keywords (else unknown), fix_commits from
hashes in status_note/fix that git resolves (91 of 463 fixed).
- .wolf/buglog-archive.json: the 710 hook auto-detections, verbatim.
- .wolf/buglog.json is now an index generated from the records, keeping
the fields OpenWolf's hooks and `openwolf bug search` read.
- scripts/buglog.py rewritten: new (template + Environment collected from
the machine and --binary), check, status (refuses a status the record
doesn't support; fixed needs Root cause, Fix, Verification and
--commit hashes git resolves), note, recur, set, show, list, triage,
env, index. 29 unittest cases in scripts/tests/test_buglog.py.
- scripts/git-hooks/pre-commit runs `check --staged`: incomplete staged
records, a legacy record hand-changed to fixed without the fix-time
sections, a new record claiming legacy: true, or a stale index refuse
the commit.
- scripts/gitea-sync.py reads the records: issue body = the record's
sections plus linked fix commits (origin remote, GITEA_COMMIT_REPO to
override), and a body hash so an issue's text is refreshed when the
record changes.
- bug-1866 rewritten to the full standard as the worked example.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | fix_commits | legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1630 | fixed | 2026-09-24 | tooling | unknown | 2026-08-23T08:35:55 | 2026-09-19T09:00:00Z | 1 |
|
|
|
|
true |
bug-1630: buglog.json integrity: 39 duplicate bug IDs present (bug-875..bug-948)
Description
buglog.json integrity: 39 duplicate bug IDs present (bug-875..bug-948). The Stop hook's duplicate-ID validation flags this every turn. bug-908, for example, is BOTH a 2026-06-21 raft_sim.c missing-guard-clause entry AND a 2026-08-16 config-upgrade-snapshot/spec.json refactor note -- two unrelated bugs sharing one id.
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
A session on 2026-08-15..17 appended new entries using an ID counter that had been restarted (or derived from a stale/remembered max) instead of computed from the file's actual maximum numeric ID. New bugs were therefore written into the already-occupied bug-875..bug-949 range: 8 collisions dated 2026-08-15, 14 dated 2026-08-16, 22 dated 2026-08-17. This is precisely the failure mode the OpenWolf bug-logging rule warns about ('never restart from bug-001; a restarted counter collides with existing history and is unrecoverable without a git-history merge'). Discovered while generating the Aug 16-22 weekly report, where an in-window timestamp query returned an implausible id range of bug-908..bug-1624.
Fix
Housekeeping only, no code change needed: renumbering commit 755976fc (2026-08-24) already repaired all 39 duplicate IDs. Re-verified 2026-08-30 -- 1077 bug entries, 1077 unique IDs, zero collisions. This entry's own fix field was simply never backfilled after the repair landed.
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1628