docs(issues): capture source-governance audit deferrals (#025-#030) by BigSimmo · Pull Request #1072 · BigSimmo/Database

BigSimmo · 2026-07-22T06:22:21Z

Summary

The source-governance audit shipped its regression-safe subset in #1051 and deferred the rest. Those deferrals existed only in #1051's PR body and session context ΓÇö so once #1051 merges they'd effectively vanish from the repo's durable memory. This captures them in docs/outstanding-issues.md (6 rows, #025ΓÇô#030).

The important one is #025. The audit reported three ranking "gaps": review_due carries no ranking penalty, unknownCurrentnessPenalty ships at 0, and selectBestSourceRecommendation ignores governance metadata. Filing those as open tasks would have been actively harmful ΓÇö they are deliberate, measured decisions, not debt:

Blanket governance metadata boosts/penalties in selection ordering were measured on 2026-07-02 to regress the golden retrieval eval to 16/23 (doc-recall@5 1.0 ΓåÆ 0.76, mrr 0.75 ΓåÆ 0.64). The corpus is only partially metadata-enriched and normalizeSourceMetadata coerces unenriched docs to unknown/unverified ΓÇö so "unknown" Γëá "bad", and blanket weighting swings ranking ~0.35 for reasons unrelated to relevance. Even governance-as-tiebreak buried correct unenriched docs (3 designs bisected, PR #118).

So #025 is written as a guardrail with the measurement attached, not a todo ΓÇö it exists to stop a future session "fixing" a known regression back into the ranker.

The rest are genuine, correctly-scoped follow-ups:

Row	Item
`#026`	Governance metadata absent from the LLM prompt (generation-surface; needs `eval:rag` + approval; same "unknown Γëá bad" hazard)
`#027`	Answer cache can serve stale governance metadata ΓÇö already mitigated by explicit invalidation; residual risk only, next action is a regression test
`#028`	Threshold-conflict detection covers only ANC/WBC/platelets (broadening carries false-positive risk)
`#029`	No explicit `is_public` flag ΓÇö visibility is implicit `owner_id IS NULL`
`#030`	D5 `NEXT_PUBLIC_RAG_TRUST_CAP_ALL_CLAIMS` parked OFF (product decision)

Audit item 12 (canary automation) is deliberately not filed ΓÇö already covered by the blocking pr-policy RAG-impact gate plus the weekly scheduled 44-case canary. Filing it would be a false todo.

Verification

npx prettier --check docs/outstanding-issues.md ΓÇö clean
npm run docs:check-links ΓÇö passed, 1103 repo path references resolve

Docs-only; no code, no behaviour, no provider calls. The non-#025ΓÇô#030 line changes are prettier re-padding the aligned markdown table (whitespace only) because the new Detail cells are the widest in the column.

Risk and rollout

Risk: none ΓÇö documentation only.
Rollback: single-commit revert.
Provider or production effects: None.

≡ƒñû Generated with Claude Code

Summary by CodeRabbit

Documentation
- Expanded the Open items list with six newly tracked entries (IDs #032–#037), including priority/type, summaries, and next actions.
- Updated the document’s next-issue marker to reflect the next available item ID.

Sweep note

Governance audit deferrals landed as #32-#37 (not #25-#30) because main already used #25-#30 for webhook/observability items; next-id=038.

The source-governance audit (PR #1051) shipped its safe subset and deferred the rest. Those deferrals lived only in the PR body and session context, so they would have been lost once #1051 merged. Capture them in the durable ledger. Most important: #25 records that the audit's ranking findings (review_due has no ranking penalty, unknownCurrentnessPenalty ships at 0, bestSource ignores governance) are NOT debt to pay down — they are deliberate, measured decisions. Blanket governance weighting in selection ordering was measured on 2026-07-02 to regress the golden eval to 16/23 (doc-recall@5 1.0->0.76) because the corpus is only partially metadata-enriched and normalizeSourceMetadata coerces unenriched docs to unknown, so "unknown" != "bad". Filing them as open tasks would have invited a future session to re-introduce a known regression, so the row is written as a guardrail with the measurement attached. Also captured: #26 LLM-prompt governance context, #27 cache stale-governance residual, #28 threshold-conflict scope, #29 implicit is_public visibility, #30 D5 flag decision. Audit item 12 (canary automation) is deliberately not filed - already covered by the blocking pr-policy RAG-impact gate plus the weekly scheduled 44-case canary. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

supabase · 2026-07-22T06:22:26Z

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

coderabbitai · 2026-07-22T06:22:47Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c6c97b63-1d32-41e0-a365-c94553e85c97

📥 Commits

Reviewing files that changed from the base of the PR and between 28708a9 and 3164444.

📒 Files selected for processing (1)

docs/outstanding-issues.md

📝 Walkthrough

Walkthrough

The outstanding issues ledger adds open entries #032 through #037 and updates its next-ID marker from 031 to 038.

Changes

Outstanding issues ledger

Layer / File(s)	Summary
Add open issue entries and advance identifier `docs/outstanding-issues.md`	The Open items table adds entries `#032` through `#037` with descriptions, next actions, sources, and dates, while the next-ID marker advances to 038.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

BigSimmo/Database#1043: Updates the same issues ledger and advances its issue counter.
BigSimmo/Database#1046: Modifies the same Open items table and next-ID marker.
BigSimmo/Database#1073: Updates the same ledger with related issue entries and identifier metadata.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change, though the issue range is stale and doesn't match the updated `#032-`#37 entries.
Description check	✅ Passed	The description includes summary, verification, risk, and notes; only the Clinical Governance Preflight section is omitted.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch claude/capture-governance-audit-deferrals

_{Comment @coderabbitai help to get the list of available commands.}

BigSimmo · 2026-07-22T06:40:01Z

@codex fix branch conflicts please

chatgpt-codex-connector · 2026-07-22T06:42:38Z

Summary

Resolved the outstanding-issues ledger merge conflict by keeping the latest main ledger entries, preserving the source-governance audit deferrals, renumbering them to #029–#034, and advancing issues:next-id to 035. docs/outstanding-issues.mdL30-L64
Kept the merged main webhook documentation updates in the conflict-resolution commit, including the expanded webhook integration overview and setup guidance. docs/webhooks.mdL1-L11
Committed the conflict resolution on the current branch with commit a2b4d56 (docs(issues): resolve outstanding issues ledger conflict).
Created PR metadata with title: docs(issues): resolve ledger conflict on governance deferrals.

Testing

✅ git diff --check
✅ npx prettier --check docs/outstanding-issues.md
✅ npm run docs:check-links

Status

Current branch: work
Worktree: clean after commit
Push: not performed in this environment.

View task →

BigSimmo · 2026-07-22T08:23:49Z

@coded please resolve the branch conflict for me so it actually resolves it and commit and push here

BigSimmo · 2026-07-22T08:24:04Z

@codex please resolve branch conflict and commit and push here

chatgpt-codex-connector · 2026-07-22T08:27:04Z

Summary

Resolved the branch conflict by merging origin/main into the PR branch and preserving the latest ledger entries from main; the ledger now advances issues:next-id to 037. docs/outstanding-issues.mdL30-L36
Preserved the source-governance audit deferrals by renumbering them to #031–#036 after the main entries #025–#030. docs/outstanding-issues.mdL59-L66
Committed the conflict resolution locally as b3fd371 with message docs(issues): resolve outstanding issues ledger conflict.
Created PR metadata with title docs(issues): resolve ledger conflict on governance deferrals.
Push was attempted, but the environment does not have GitHub HTTPS credentials, so the push could not complete.

Testing

✅ git diff --check
✅ npx prettier --check docs/outstanding-issues.md
✅ npm run docs:check-links
⚠️git push origin HEAD:claude/capture-governance-audit-deferrals — failed because GitHub credentials are unavailable in this environment: fatal: could not read Username for 'https://github.com': No such device or address.

View task →

Co-authored-by: Cursor <cursoragent@cursor.com>

github-actions · 2026-07-22T08:54:50Z

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #4453 (success).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:21c1b72e80

ℹ️ 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".

coderabbitai

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/outstanding-issues.md`:
- Around line 61-66: Update the PR description’s stated objectives to reference
the newly added ledger entries `#032`–#037 instead of `#025`–#030. Keep the existing
issue IDs and details unchanged, and ensure the description accurately reflects
the committed changes in docs/outstanding-issues.md.
- Line 62: Update the `#033` entry in docs/outstanding-issues.md to replace the
stale cross-reference to `#025` with `#032`, leaving the governance metadata
description and surrounding issue details unchanged.
- Line 30: Restore the missing `#031` entry in docs/outstanding-issues.md between
`#030` and `#032`, or consistently renumber the affected rows and issues:next-id
marker together. Update the `#033` entry’s reference from `#025` to `#032` while
preserving the ledger’s sequential numbering.

🪄 Autofix (Beta)

❌ Autofix failed (check again to retry)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 43766263-fc68-4a7f-b8fb-5a1180313fd8

📥 Commits

Reviewing files that changed from the base of the PR and between eb2a83c and 21c1b72.

📒 Files selected for processing (1)

docs/outstanding-issues.md

BigSimmo · 2026-07-22T09:01:14Z

@codex Connector push test: resolve the current merge conflict by merging origin/main into the existing PR branch claude/capture-governance-audit-deferrals, preserve both the current main ledger entries and this PR's governance deferrals, create one conflict-resolution commit, and push that commit to the same PR branch. This explicitly authorizes GitHub read/write operations for PR #1072. Do not rebase, force-push, merge the PR, change unrelated files, or create a second PR. Reply with the pushed commit SHA or the exact push failure.

chatgpt-codex-connector · 2026-07-22T09:03:51Z

Summary

Merged state was already present on claude/capture-governance-audit-deferrals, so I made a single follow-up conflict-resolution commit on that same PR branch: 84ad8dcd26908493c96c2fd2d1d97b17ece2ddd0.
Preserved the latest main ledger entries through #030, restored sequential numbering by placing the governance deferrals at #031–#036, and advanced issues:next-id to 037. docs/outstanding-issues.mdL30-L66
Fixed the stale governance cross-reference so the LLM-prompt deferral now points at the adjacent governance-ranking guardrail #031, not the unrelated #025. docs/outstanding-issues.mdL61-L62

Push result

❌ Exact push failure: fatal: could not read Username for 'https://github.com': No such device or address
The local branch is ahead by 1 commit; the commit that needs pushing is 84ad8dcd26908493c96c2fd2d1d97b17ece2ddd0.

Testing

✅ git diff --check
✅ npx prettier --check docs/outstanding-issues.md
✅ npm run docs:check-links
❌ git push origin HEAD:claude/capture-governance-audit-deferrals — failed because GitHub HTTPS credentials are unavailable in this environment: fatal: could not read Username for 'https://github.com': No such device or address

View task →

Co-authored-by: Cursor <cursoragent@cursor.com>

coderabbitai · 2026-07-22T09:11:12Z

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

❌ Failed to clone repository into sandbox. Please try again.

Co-authored-by: Cursor <cursoragent@cursor.com>

BigSimmo enabled auto-merge (squash) July 22, 2026 06:34

BigSimmo disabled auto-merge July 22, 2026 07:20

BigSimmo enabled auto-merge (squash) July 22, 2026 07:20

coderabbitaiBot mentioned this pull request Jul 22, 2026
docs: re-diagnose #018 (generation not retrieval), close #019, add #022 governance worklist #1073
Merged

Merge origin/main; renumber governance deferrals to#32-#37
21c1b72
Co-authored-by: Cursor <cursoragent@cursor.com>

chatgpt-codex-connectorBot reviewed Jul 22, 2026
View reviewed changes

Comment threaddocs/outstanding-issues.md Outdated

coderabbitaiBot reviewed Jul 22, 2026
View reviewed changes

Comment threaddocs/outstanding-issues.md
Comment threaddocs/outstanding-issues.md Outdated
Comment threaddocs/outstanding-issues.md Outdated

BigSimmoand others added 2 commits July 22, 2026 17:06

style(docs): prettier-format outstanding-issues after merge renumber
28708a9
Co-authored-by: Cursor <cursoragent@cursor.com>

Merge branch 'main' into claude/capture-governance-audit-deferrals
beec72c

docs(issues): retarget#33governance cross-ref from#25to#32
3164444
Co-authored-by: Cursor <cursoragent@cursor.com>

BigSimmo merged commit f93395d into mainJul 22, 2026
57 checks passed

BigSimmo deleted the claude/capture-governance-audit-deferrals branch July 22, 2026 09:14

This was referenced Jul 24, 2026
docs: record canary comparison preflight #1180
Merged
fix(deps): pin brace-expansion 5.x to the patched 5.0.8 #1314
Merged
fix(documents): recount facets against the current selection, and capture five search-filter findings #1526
Merged

coderabbitaiBot mentioned this pull request Aug 7, 2026
docs(issues): confirm #256's dead section sets; capture two mode-nav follow-ups #1685
Merged
2 tasks

Conversation

BigSimmo commented Jul 22, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Verification

Risk and rollout

Summary by CodeRabbit

Summary by CodeRabbit

Sweep note

Uh oh!

supabaseBot commented Jul 22, 2026

Uh oh!

coderabbitaiBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

BigSimmo commented Jul 22, 2026

Uh oh!

chatgpt-codex-connectorBot commented Jul 22, 2026

Uh oh!

BigSimmo commented Jul 22, 2026

Uh oh!

BigSimmo commented Jul 22, 2026

Uh oh!

chatgpt-codex-connectorBot commented Jul 22, 2026

Summary

Uh oh!

github-actionsBot commented Jul 22, 2026

CI triage

Uh oh!

chatgpt-codex-connectorBot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

coderabbitaiBot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

BigSimmo commented Jul 22, 2026

Uh oh!

chatgpt-codex-connectorBot commented Jul 22, 2026

Summary

Push result

Uh oh!

coderabbitaiBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

BigSimmo commented Jul 22, 2026•
edited by coderabbitai Bot
Loading

coderabbitaiBot commented Jul 22, 2026•
edited
Loading

coderabbitaiBot left a comment •
edited
Loading

coderabbitaiBot commented Jul 22, 2026•
edited
Loading