fix(B-0441): re-open per parent-child status invariant (B-0532)

[AceHack]

Summary

Restores B-0441 to status: open to satisfy the --enforce-parent-child-status lint (B-0532 gate). PR #3942 closed B-0441 while child B-0460 (slice 5.2 — subscriber handler) was still open; the lint failure surfaced this correctly but auto-merge fired anyway because the lint check isn't in the required-checks list.

This PR brings origin/main back to parent-child consistency.

Why the previous close was wrong

The 2026-05-16 acceptance-refresh PR (#3942) marked 6 stale unchecked acceptance boxes as [x] correctly — the notifier-side IS fully implemented. But it ALSO flipped status: closed, which violated the parent-child invariant because children: [B-0500, B-0501, B-0502, B-0460] includes one open child (B-0460).

The audit output was unambiguous:

## 9. Parent-child status mismatch (B-0532)
Parent-child status-mismatch groups: 1
- B-0441 (closed) has open children:
- Re-open the parent if the children represent unfinished work, OR
- Remove the child refs from the parent's `children:` if they no longer apply
error: 1 parent-child status-mismatch group(s) found; --enforce-parent-child-status set (B-0532 gate)

I picked "re-open the parent" because B-0460 IS unfinished work (subscriber handler scope is genuinely different from notifier scope; both lanes are legitimate).

Diff

• docs/backlog/P1/B-0441-*.md:
  • status: closed → status: open (one line)
  • Added a new ## Closure status (2026-05-16) section explaining notifier-side is complete (acceptance refresh stands) but row stays open per parent-child invariant until B-0460 lands
• docs/BACKLOG.md: regenerated — flips back [x] → [ ] for B-0441 line

Test plan

• lint (backlog parent-child status) passes (verified locally: 0 mismatch groups)
• Audit doesn't surface any new violations
• When B-0460 lands later, a follow-up PR can flip B-0441 to closed without further substrate work

Open question for human maintainer

The lint (backlog parent-child status) check failed on PR #3942 but auto-merge fired anyway. This suggests the check is NOT in the required-checks list. If parent-child consistency matters (the B-0532 design implies it does), the check should likely be required. That's a separate decision — flagging for awareness, not addressing here.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8e8f1611ca

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Copilot]

Pull request overview

This PR restores backlog parent/child status consistency by re-opening B-0441 (parent) while child work (notably B-0460) remains open, and updates the generated backlog index accordingly.

Changes:

• Re-opened B-0441 (status: open) and updated last_updated to 2026-05-16.
• Added a “Closure status (2026-05-16)” note to explain why the row remains open despite progress.
• Regenerated docs/BACKLOG.md to reflect the row’s open status.

Reviewed changes

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

File	Description
docs/backlog/P1/B-0441-backlog-row-ready-to-grind-notifier-background-service-2026-05-13.md	Re-opens the parent row and adds a closure/status explanation section.
docs/BACKLOG.md	Regenerated index reflecting B-0441 as open.

Comments suppressed due to low confidence (1)

docs/backlog/P1/B-0441-backlog-row-ready-to-grind-notifier-background-service-2026-05-13.md:184

• The closure note says the notifier-side is complete and that all acceptance criteria are checked, but the parent acceptance list includes the assignment-history cooldown criterion (slice 5a) which is still tracked as open in B-0501 and not implemented in tools/bg/backlog-ready-notifier.ts. Update this note to reflect the remaining unshipped notifier-side work, or align the acceptance checklist/child statuses with what’s actually shipped.

## Closure status (2026-05-16)

**Notifier-side: complete.** All 8 acceptance criteria checked (slices 1, 2, 3, 4, 5a, 6 shipped per the decomposition table; tests in `tools/bg/backlog-ready-notifier.test.ts`; launchd plist via B-0502; docs in `docs/AUTONOMOUS-LOOP.md`). Empirically confirmed live during the 2026-05-16 session via `bun tools/bg/backlog-ready-notifier.ts --once` — returned the documented JSON shape with `queueBusy: true` correctly suppressing publication.

**Row stays `status: open`** because child **B-0460** (slice 5.2, agent-side subscriber handler) is genuinely the remaining unshipped scope, and the `--enforce-parent-child-status` lint (B-0532 gate) correctly requires parent rows to stay open while any child is open. Closing this row would violate that invariant.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 096774ea47

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.