docs(devlog): record 2026-10-04 merge activity

[devin-ai-integration]

Summary

• Adds devlog/_fin/261004_merge_record/ continuing the 261002 release-merge record to cover landings on dev from b4616be1e (chore(release): open dev at 2.77.0 before releasing 2.76.0 lidge-jun/opencodex#6462 dev-open at 2.77.0) through 584b92a5 (test(layout): compact the test-layout fixture to restore ratchet headroom lidge-jun/opencodex#6583): 47 first-parent landings partitioned into 11 recorded here, 35 covered by existing documentation units, and 1 release dev-open.
• 000_scope.md: fixed boundaries, disjoint partition counts (47 = 11 + 35 + 1), method and limits — same format as the maintainer-endorsed 261002_release_merge_record (linked pinned to its unlanded carry commit 567d414ddf on this fork).
• 010_releases.md: v2.77.0 published 2026-10-04 02:40:47 UTC (Release run 37170949169, tag commit 06841165f8, no preview tag), 2.77.0 dev content range e0af52c8a2..0818ea181 (32 first-parent), and the train-recovery dispatch candidate CI (Cross-platform run 37110109894, success).
• 020_landings.md: the 11 uncovered landings (Windows train tail fix(update): normalize short Windows home paths for Scoop npm lidge-jun/opencodex#6494/test: drain Windows ACL work and startup child output lidge-jun/opencodex#6495, combo refusal repair fix(combo): preserve bounded nested HTTP refusal semantics lidge-jun/opencodex#6540, unrecorded follow-ups fix(claude): preserve bounded large headers in picker relay lidge-jun/opencodex#6551/fix(devin): qualify child trajectories by supplied parent lidge-jun/opencodex#6565, the four next-release-261004-catalog-a* merges fix(codex): require saved config authority for routed removal lidge-jun/opencodex#6553/fix(codex): bind catalog writes to home ownership and intent lidge-jun/opencodex#6558/feat(codex): audit catalog writes with bounded private records lidge-jun/opencodex#6560/feat(codex): heal lost catalog rows only from the idle owner lidge-jun/opencodex#6563, and feat(gui): icon theme switch sharing a row with the zoom stepper lidge-jun/opencodex#6579/test(layout): compact the test-layout fixture to restore ratchet headroom lidge-jun/opencodex#6583), plus the 35 covered landings mapped to their eleven existing units, and dev-open chore(release): open dev at 2.78.0 before releasing 2.77.0 lidge-jun/opencodex#6549.
• Placed under _fin/ matching where the maintainer moved the 261002 merge record; it is a closed historical record that cross-references rather than repeats the stabilization unit's release account.

Verification

• git rev-list --first-parent --count b4616be1e..584b92a53 = 47; each landing's merge subject and merge_commit_sha cross-checked against the GitHub API; every covered PR greps to a devlog unit or landed devlog files.
• All 24 intra-devlog links verified to exist on disk; release tag/published-at/asset data and both Actions runs fetched from the upstream GitHub API.
• Docs-only record: no code changed, so no unit/typecheck suite applies; validation was the deterministic inventory and link checks above.
• Branched off dev tip 584b92a5, 0 behind at push. CodeRabbit skipped review on bot-author detection; the Devin Review flag — broken 261002_release_merge_record predecessor link — was fixed in e08ed92ef by pinning the link to the carry commit.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Link to Devin session: https://app.devin.ai/sessions/d678536cbf444bd392c2cd696c02348b
Open in Devin Desktop: https://app.devin.ai/desktop/session/d678536cbf444bd392c2cd696c02348b?variant=devin
Requested by: @luvs01

Review readiness checklist

This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:

• Required local validation passed; commands, results, and any full-suite exception are documented.

• I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).

• I resolved all correct Codex and CodeRabbit findings.

• My PR is ready for review.

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: luvs01/opencodex/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 080aaa38-04ef-4a05-aa59-cfc23c50babc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[devin-ai-integration]

✅ Devin resolved the finding on 92baafa

Fixed by Devin (1)

• Predecessor record link is broken

View all findings in Devin Review

[github-actions]

✅ READY

• all PR quality gates passed; the review readiness checklist is complete.

Review readiness checklist

• ✅ Required local validation passed; commands, results, and any full-suite exception are documented.
• ✅ I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
• ✅ I resolved all correct Codex and CodeRabbit findings.
• ✅ My PR is ready for review.

✅ 4/4 boxes ticked.

This pull request is already Ready for Review.
The review-ready label marks this PR as ready; review automation runs independently.
Maintainers: @lidge-jun @Ingwannu