chore(ledger): queue duplicate closures, correct #ES3KTG's outcome, record the #8CKX6F ruling

Merged
BI
1mo ago
+79-0

User description

Summary

Follow-up to #3625 (whose reconcile created these rows). Queued only through scripts/ledger-inbox.mjs; applied by the next issues:reconcile. No hand ledger edits, no CRAFT change.

  • done #WWV98H: duplicate of #WWTRM5 (#WMGPSG doc/decision drift)
  • done #YJXRS3: duplicate of #8Y9169 (PR 3538 leftovers after 13 Nov)
  • done #BDFFYF: duplicate of #Z12CBC (Form 6A/6B sign-off or removal; #Z12CBC carries the 17 Oct 21:37 AWST owner decision)
  • done #GKAEZS: duplicate of #C4Q3T7 (audit M5-2 calculator mockups; flagged by qodo on #3625)
  • amend-outcome #ES3KTG: replaces the unrelated upload-validation outcome (from #3617 request f175ee1d) with the rag-coverage-gate evidence (raw + corrected tokens; aligned stop-drug vocabulary; tests/rag-coverage-gate.test.ts)
  • docs/decisions/2026-10-18-no-national-youth-crisis-line-pinning-yet.md: the 18 Oct 00:10 AWST #8CKX6F ruling (requested by gitar on #3625)
  • Regenerated repo-awareness snapshot

Areas touched: Docs / ledger

Verification

  • Checks run: ledger-inbox.mjs check → Ledger inbox check passed: 10 pending request(s), 2139 applied.; check:decisions → 0 errors, 0 warnings; check:repo-awareness-snapshot → in step; each duplicate verified against the surviving row on main.

Risk and rollout

  • Risk: ledger text only.
  • Rollback: cancel the queued requests via ledger-inbox.mjs cancel.
  • Provider or production effects: None

Notes

  • No clinical sign-off recorded; no code change.

Summary by cubic

Queues ledger closures and one record entry via scripts/ledger-inbox.mjs, applied by the next issues:reconcile; no hand ledger edits or CRAFT changes.

Closes #WWV98H, #YJXRS3, #BDFFYF, and #GKAEZS as duplicates of their surviving rows; corrects #ES3KTG's outcome to the rag-coverage-gate evidence; records the 18 Oct owner ruling against pinning national youth crisis lines, leaving whether it covers the existing adult_metro_crisis route, where Lifeline WA sits third for "youth self harm", as an open owner question; regenerates the repo-awareness snapshot.

CodeAnt-AI Description

Record issue updates and clarify the youth crisis-line pinning decision

What Changed

  • Queues four duplicate issue closures for the next ledger reconciliation
  • Corrects the recorded outcome for the clozapine blood-action search gate
  • Documents that national youth crisis lines will not be pinned for CAMHS crisis searches until the owner approves a list; no routing changes are made

Impact

✅ Clearer tracking of duplicate issues
✅ Corrected clozapine search-gate record
✅ Documented youth crisis-line approval requirement

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