---
id: "bug-1630"
status: "fixed"
status_updated: "2026-09-24"
status_note: ""
component: "tooling"
severity: "unknown"
timestamp: "2026-08-23T08:35:55"
last_seen: "2026-09-19T09:00:00Z"
occurrences: 1
files: [".wolf/buglog.json"]
tags: ["buglog", "openwolf", "data-integrity", "duplicate-id", "tooling", "needs-git-history-merge", "verified-2026-08-30"]
related: ["bug-1628"]
fix_commits: ["755976fc"]
legacy: 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