ledger: keep #WFYDV6 open per owner decision; #8Y9169 correction (replaces #3616)

Merged
BI
1mo ago
+87-0

User description

Replaces #3616. This is a clean branch from main. It leaves out 99439a8ac, a bot commit that hand-edited docs/outstanding-issues.md and the snapshot, which failed ledger write discipline.

Owner decision (17 Oct 2026, 21:37 AWST): #WFYDV6 (the unwired WA MHA Form 6A/6B print form with unverified statutory text) stays open. The form stays unwired until owner, legal and clinical sign-off.

Changes (inbox requests only; the canonical ledger is untouched until the next serialized issues:reconcile):

  • a5c25ca4: P1 add that reopens the #WFYDV6 work by owner decision; f8628e25: amend-outcome on the archived #WFYDV6 row pointing to the reopen
  • 15a11955: P3 correction for the #3570 branch-review record
  • c455b372: issues:update of #8Y9169 with the corrected inventory. The recalculate script's test runs in the suite, and the attendance roster and QR check-in helper are wired. This is the same correction 99439a8ac wrote directly.
  • 177b7474: P3 task to add a ledger reopen action that keeps the original ID and ULID. The tooling has none today, so the reopen uses add + amend-outcome.
  • docs/decisions/2026-10-17-wfydv6-stays-open-until-sign-off.md: records the decision and states that the Form 6A/6B wording still needs owner, legal and clinical sign-off

Carries over #3616's two Codex threads: the decision entry (P1) and the #WFYDV6 identity (P2), which is tracked by the P3 reopen task. Reconciling the three #3609 follow-ups is left to the next reconcile run.

Checks run locally: ledger write discipline, outstanding-issues, decisions, organisation, docs index/inventory, repo-awareness snapshot, and 6 ledger/decision test files (141 tests).

Summary by cubic

Replaces #3616 with a clean branch from main that keeps ledger issue #WFYDV6 open per the owner's decision on 17 Oct 2026; PR #3609 had archived it without the required owner, legal and clinical sign-off. All changes are inbox requests; the canonical ledger is untouched until the next serialized issues:reconcile.

  • Re-tracks #WFYDV6 as a new open P1 row (add) and records the reopen on the archived row (amend-outcome), since the ledger tooling has no reopen action.
  • Queues a P3 task to add a ledger reopen action that moves an archived row back to the open table with its original ID and ULID; it lands with tests in its own PR. A review bot's unreviewed attempt to implement that action was reverted.
  • Queues a P3 correction for the #3570 record's branch name and an issues:update with the corrected #8Y9169 inventory (the recalculate script's test stays in the suite; attendance roster and QR check-in helper are wired).
  • Adds a decision doc anchoring the reopen and stating the Form 6A/6B wording still needs owner, legal and clinical sign-off.

CodeAnt-AI Description

Keep WA MHA Form 6A/6B unwired until required sign-off

What Changed

  • Records the owner’s decision to keep the Form 6A/6B print form unwired and its issue open until owner, legal and clinical sign-off; queues the issue and archived-row update for the next ledger reconciliation.
  • Corrects the pending #8Y9169 inventory, including the wired attendance roster, QR check-in helper and clinical editor.
  • Queues a correction to the #3570 branch name and a task to add a ledger action that reopens issues with their original identity.

Impact

βœ… Form 6A/6B sign-off requirement recorded
βœ… #8Y9169 inventory reflects which tools are wired
βœ… Ledger corrections queued for reconciliation

πŸ’‘ 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.