chore(ledger): fold the #WFYDV6 split back into one identity via ledger-inbox reopen

Merged
BI
1mo ago
+56-3

User description

Summary

  • Folds the #WFYDV6 split back into one identity, using only ledger-inbox requests (no hand edits to the ledger). These are new request files to be applied by the next npm run issues:reconcile:
    • reopen #WFYDV6: moves the archived row back to the open table as P1 with its original ID and ULID. It carries the owner-decision detail from the duplicate row, and the reopen action keeps the prior archived outcome in the detail.
    • done #Z12CBC: closes the duplicate identity that #3625 added (from request a5c25ca4) before the reopen action existed, recorded as folded back into #WFYDV6.
    • done #GYR7Q3: closes ledger task 177b7474; the reopen action landed in #3627.
  • Updates the tracking-mechanism sentence in docs/decisions/2026-10-17-wfydv6-stays-open-until-sign-off.md to describe the reopen in place. The decision is unchanged: #WFYDV6 stays open and the form stays unwired until owner, legal and clinical sign-off.

Areas touched: Knowledge and records

Verification

  • Checks run: ledger-inbox reconcile --dry-run → Would reconcile 8 request(s) into docs/outstanding-issues.md. ledger-inbox check → Ledger inbox check passed: 8 pending request(s), 2139 applied. No pending request from another session touches #WFYDV6, #Z12CBC or #GYR7Q3. All Static PR checks steps pass locally, including check:outstanding-issues, check:ledger-write-discipline, check:decisions and check:knip. vitest run tests/ledger-inbox.test.ts tests/decisions*.test.ts: 54 passed.

Risk and rollout

  • Risk: low. These are queued ledger requests and one decision-doc sentence.
  • Rollback: revert the commit before reconciliation, or queue a cancel for each request.
  • Provider or production effects: None

Notes

  • Signs nothing off. The Form 6A/6B statutory wording still needs owner, legal and clinical sign-off.
  • Follow-up to #3627.

Summary by cubic

Folds the #WFYDV6 ledger split back into a single identity by queuing four ledger-inbox requests (applied by the next npm run issues:reconcile), with no hand edits to the ledger.

  • reopen #WFYDV6 moves the archived row back to the open table as P1 with its original ID and ULID, carrying the owner-decision detail from the duplicate row.
  • done #Z12CBC closes the duplicate identity added before the reopen action existed, recorded as folded back into #WFYDV6.
  • done #BDFFYF folds the separate sign-off tracker #BDFFYF into the reopened #WFYDV6.
  • done #GYR7Q3 closes the ledger task for the reopen action that landed in #3627.
  • Updates the tracking-mechanism sentence in docs/decisions/2026-10-17-wfydv6-stays-open-until-sign-off.md. The decision is unchanged: #WFYDV6 stays open until owner, legal, and clinical sign-off, and nothing here signs the form off.

Migration

  • Risk is low; roll back by reverting the commit before reconciliation or queue a cancel for each request.

CodeAnt-AI Description

Reopen #WFYDV6 in place and fold duplicate tracking into one issue

What Changed

  • Queues #WFYDV6 to reopen as a P1 under its original identity, with the owner’s decision details.
  • Folds duplicate #Z12CBC into #WFYDV6 and closes the completed #GYR7Q3 tracking task.
  • Clarifies that the form remains unwired and the issue stays open until owner, legal, and clinical sign-off.

Impact

✅ One tracking identity for #WFYDV6
✅ #WFYDV6 stays open as a P1 pending sign-off
✅ Duplicate tracking entries closed

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