chore(ledger): reopen #WFYDV6 by owner decision and reconcile #3609 follow-ups

Closed
BI
1mo ago
+121-4

User description

Follow-up to #3609 applying the owner decisions of 17 Oct 2026 21:37 AWST, via the ledger inbox only (no hand edits, no guard skips, no --allow-concurrent).

  • Reconcile the three follow-ups #3609 queued (now open rows): PR 3538 leftovers split from #08216B, remaining #WMGPSG drift items, older calculator mockups split from #1WAA0Z.
  • Queue reopen of #WFYDV6 (WA MHA Form 6A/6B statutory text): a P1 add re-tracking it until legal and clinical sign-off, plus an amend-outcome on the archived row recording the reopen. The ledger tooling has no in-place reopen action, and the write-discipline guard requires requests to land on main before reconciliation, so these apply at the next serialized issues:reconcile.
  • Queue a P3 ledger-correction task: the #3570 prlanded record (added by #3609) names branch claude/reconcile-inbox-20261016; the actual head branch was claude/reconcile-ledger-20261016 (SHAs correct).

No code changes. wa-mha-form-print.tsx remains unimported.

Summary by cubic

Reconciles the ledger follow-ups from #3609 on main and applies the 17 Oct owner decision to reopen #WFYDV6, all through the ledger inbox.

  • The snapshot gains three rows split from #08216B, #WMGPSG, and #1WAA0Z (open count 108 → 111).
  • A P1 add plus an amend-outcome on the archived row re-track #WFYDV6 as open until legal and clinical sign-off; wa-mha-form-print.tsx stays unwired. The decision is anchored in a new docs/decisions/2026-10-17-wfydv6-stays-open-until-sign-off.md.
  • A P3 task queues a branch-name correction for the #3570 prlanded record (SHAs are correct), and a second P3 task asks for a ledger reopen action that keeps the original ID and ULID.
  • The #8Y9169 cleanup-task inventory text is corrected through a queued issues:update instead of a direct ledger write.
  • Entries apply at the next serialized issues:reconcile. No code changes.

CodeAnt-AI Description

Reopen tracking for unverified WA MHA forms and retain unresolved follow-ups

What Changed

  • Queues reopening #WFYDV6 as a P1 until the WA MHA Form 6A/6B text receives legal and clinical sign-off; the print component remains unwired.
  • Keeps three unresolved follow-ups from archived issues as separate open entries.
  • Queues a correction to the branch name recorded for PR #3570.

Impact

✅ WA MHA form sign-off risk remains tracked as P1
✅ Three unresolved follow-ups remain visible as open items
✅ PR #3570 branch-record correction is queued

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by CodeRabbit

  • Documentation
    • Updated the outstanding-issues snapshot to 17 October 2026, with 111 open items.
    • Added tracking for remaining cleanup, documentation and instruction corrections, and a review of older calculator mockups.
    • Reopened a high-priority issue: the WA MHA Form 6A/6B print component remains unwired pending legal and clinical sign-off.
    • Added tasks to correct a recorded branch name through the approved process and to support reopening archived issues.