chore: batch buglog entries for the 2026-08-29 merges

[sakibsadmanshajib]

Summary

This is the batched buglog follow-up for the pull requests merged to main on 2026-08-29. Its diff is .wolf/buglog.jsonl and nothing else.

Per .claude/rules/openwolf.md, every fixed bug, error, failed test or failed build must be logged, but the line may never be appended on a fix branch. merge=union in .gitattributes resolves concurrent appends locally and is ignored by GitHub's server side merge, so two branches that both appended land in hard conflict there. An unmergeable pull request gets no refs/pull/N/merge, no pull_request run and therefore zero checks, and the required status gate then blocks the merge for a reason the page never states (issue #873). Each fix accordingly carried its entry in its own pull request body, and this pull request copies them onto main in one batch, which the protocol explicitly prefers over one pull request per entry.

Scope examined

Sixty one pull requests merged to main on 2026-08-29. Fifty of them carried at least one entry, for eighty five entries in total. Thirty two of those were already on main and are skipped, leaving fifty three appended here from thirty six pull requests.

#1432 and #1448 merged after the first enumeration pass and were folded in afterwards, in a second commit on this branch.

The largest block of skips comes from #1342, the equivalent batch for the 2026-08-28 merges, which merged earlier the same day and already landed thirty six entries covering #1257, #1268, #1276, #1277, #1287, #1292, #1293, #1294, #1296, #1301, #1303, #1305, #1313, #1335 and #1337.

What landed

Fifty three entries appended, one JSON object per line, append only. The 232 pre-existing lines are byte identical to origin/main (verified by hashing the first 232 lines of the result against the base file). Every line in the resulting file parses as JSON and carries error_message, root_cause, fix and tags.

Source	Entries
#1083	2
#1277	1
#1278	1
#1298	1
#1334	1
#1336	3
#1343	1
#1346	1
#1351	1
#1365	2
#1368	1
#1369	1
#1371	3
#1375	3
#1376	1
#1378	1
#1379	2
#1388	5
#1389	3
#1390	2
#1393	1
#1394	1
#1410	1
#1417	1
#1421	1
#1423	1
#1424	1
#1426	1
#1429	1
#1431	1
#1432	2
#1433	1
#1434	1
#1436	1
#1439	1
#1448	1 (reformatted, see below)

Entries are copied verbatim from their source pull request bodies. Nothing was rewritten, no field was invented, and no field was added.

One entry needed repair. #1448 wrote its Buglog entry section as prose key and value lines (error_message: ..., root_cause: ...) rather than as a JSON object, so it was reformatted into a single line here. Every value is its author's own text with the body's line wrapping unwrapped, and the id, date, title, verification, tags and pr keys it named are preserved. Nothing was added and nothing was dropped. The other eighty four extracted entries parsed as JSON on the first attempt with all four required fields present.

Merged pull requests that carried no entry

Eleven of the sixty one. Recorded here because the gap is itself the useful signal.

Pull request	Title	Assessment
#1013	chore(deps): bump the go-minor-patch group across 1 directory with 4 updates	Dependabot bump, no defect fixed, no entry expected
#1015	chore(deps): bump the go-minor-patch group across 1 directory with 6 updates	Dependabot bump, no entry expected
#1016	chore(deps): bump golang from 1.26-alpine to 1.27-alpine in /deploy/docker	Dependabot bump, no entry expected
#1218	chore(deps): bump postcss from 8.5.19 to 8.5.26 in /apps/desktop	Dependabot bump, no entry expected
#1219	chore(deps): bump golang.org/x/crypto from 0.41.0 to 0.52.0 in /apps/control-plane	Dependabot bump, no entry expected
#1342	chore: batch buglog entries for the 2026-08-28 merges	The previous batch pull request itself, correctly carries no entry of its own
#1364	chore: remove four dead skills and record the patterns that cost time	Protocol gap. The body records patterns that cost time, which is the shape of a buglog entry, but none was written as one
#1383	test: retire stale expected-failure markers, restore the ones that are true (#1381, #1382, #1324)	Protocol gap. Stale it.fails markers reading as red is a real defect that was fixed here and should have carried an entry
#1384	docs: correct D-047, hive-auto reverted to variable pricing (D-059)	Decision ledger correction, arguably a documentation defect, no entry written
#1387	chore(deps): bump next from 15.5.23 to 16.3.3 in /apps/agent-console	Dependabot bump, no entry expected
#1398	docs: rescue the 2026-08-25 parity captures and add the 2026-08-29 QA matrix evidence	Documentation and evidence rescue, no entry written

Six of the eleven are Dependabot bumps and one is the previous batch, so the genuine protocol gaps are #1364, #1383, #1384 and #1398. Of those, #1383 is the one worth a follow-up: it fixed a real defect class (a stale expected-failure marker reads as a red "Expect test to fail" and gets dismissed as pre-existing) and left no record.

A twelfth pull request, #1448, is not counted as a gap. It did write an entry, just not as JSON; see the repair note above.

Entries skipped as already present

Thirty two. Thirty of them matched an entry already on main on error_message, id or fix. Two more from #1278 are semantic duplicates that an exact match would have missed, and were skipped after reading the landed entries they duplicate:

• test: add Anthropic Messages API conformance suite using the real SDK #1278's streaming content_block_start omits text field entry is covered by the consolidated bug-2026-08-28-anthropic-sdk-wire-conformance entry landed from fix: make the Anthropic surface conform to the real SDK wire contract (#1274, #1260, #1261, #1259) #1296, whose root cause names the same omitempty on StreamContentBlock.Text.
• test: add Anthropic Messages API conformance suite using the real SDK #1278's GET /v1/models leaked an upstream provider name entry is covered by BUG-1284, landed from fix: keep upstream provider identity out of catalogue metadata (#1284) #1300, which names the same public.model_aliases.summary publication path.

#1278's third entry, on top_k forwarding producing a 400, is not covered anywhere on main and is appended here. #1342 recorded #1278 as fully "merged into #1296", which was accurate for two of its three entries.

Note on entry quality

One appended entry is thin: #1277's parity re-score record carries error_message of n/a and a root cause of "console had no privacy/data-policy surface at all". It is a parity gap record rather than a defect record. It is included exactly as written rather than embellished, per the protocol's preference for the author's own words.

Test plan

• Branch cut fresh from origin/main, diff is .wolf/buglog.jsonl and nothing else
• First 232 lines byte identical to the base file (md5 match)
• All 285 resulting lines parse as JSON and carry error_message, root_cause, fix and tags
• No .wolf/ telemetry (anatomy.md, memory.md, token-ledger.json, hooks/_session.json, buglog.json) in the commit
• The six required checks report green via the inert path allowlist in .github/workflows/ci.yml

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

Next included review available in 43 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9f0a7951-a71e-4d96-a788-6259bcc4110f

📥 Commits

Reviewing files that changed from the base of the PR and between 774008d and fbf70a9.

📒 Files selected for processing (1)

• .wolf/buglog.jsonl

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}