docs(gap): refresh register after stack drain and #230 merge - #236
docs(gap): refresh register after stack drain and #230 merge#236seonghobae wants to merge 1 commit into
Conversation
Records the near-zero queue (2 PRs), advances GAP-009 to partial with protected-main authority a69eb3e (posterior log-ratio edge estimator with exact Fisher-z p-values, BH step-up admission, percentile-bootstrap uncertainty, parameterised consensus resampling), and names the remaining closure evidence: Leiden consensus (Traag et al., 2019), production-scale known-truth recovery, and reproducible exports into the end-to-end run.
|
Warning Review limit reachedNext included review available in 36 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| **Snapshot:** 2026-08-25T07:47:32Z | ||
| **Protected-main evidence:** `cf0e0ad74d23c5d2e0e33d389bb0bb4d37067c31` (full SHA fetched live before every mutation) | Signal | Snapshot evidence | Delivery implication | |
There was a problem hiding this comment.
🟡 Refreshed snapshot header left atop stale PR counts
The added second **Snapshot:**/**Protected-main evidence:** header repeating the 07:47:32Z refresh now heads the old table, which still reports 59 open and 33 draft PRs (product-technical-gap-baseline.md). These contradict the refreshed 2-open/1-draft counts above, leaving two conflicting censuses in one register.
Prompt for agents
The refresh updated the first snapshot-facts table (Open pull requests 2, Draft 1) but left a duplicated snapshot/evidence header (the added lines) followed by the previous snapshot-facts table that still reports Open pull requests 59, Draft 33, Non-draft 0, etc. The two tables now contradict each other under the same 07:47:32Z timestamp. Remove the duplicated header block and the stale second table so only one current snapshot-facts table remains, or reconcile the second table's counts (open PRs, drafts, non-draft) with the refreshed figures. Also confirm whether the removed '## Purpose' and '## Snapshot facts' section headings should be restored, since deleting them left the second table without a section context.
Was this helpful? React with 👍 or 👎 to provide feedback.
| **Snapshot:** 2026-08-25T07:47:32Z | ||
| **Protected-main evidence:** `cf0e0ad74d23c5d2e0e33d389bb0bb4d37067c31` (full SHA fetched live before every mutation) | Signal | Snapshot evidence | Delivery implication | |
There was a problem hiding this comment.
🔍 Refresh silently dropped Purpose and Snapshot-facts sections
The refresh deleted the entire ## Purpose narrative and the ## Snapshot facts heading. The surviving second table now has no section heading. The PR describes only a count/SHA refresh, so this structural deletion may be unintended.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Superseded by the post-#239 refresh: base cf0e0ad predates the #239 merge that aligned versions to 0.2.0 and landed network-repair semantics. The replacement PR carries an equivalent register refresh plus CHANGELOG [Unreleased] dedup, re-fetched exact-head SHAs for the seven-PR queue, and closure states for issues #156/#168/#175. |
Summary
Refreshes
docs/product-technical-gap-baseline.mdagainst live GitHub state at 2026-08-25T07:47:32Z:a69eb3e2…via #230) with exact Fisher-z p-values, Benjamini–Hochberg step-up admission on exact p-values, percentile-bootstrap uncertainty, per-replicate stability admission, and an explicit fail-closed perturbation parameter for consensus resampling — no heuristic constants.Validation
validate_documentation.py: PASS (inventory rows == declared counts; no queued-checks-as-shipped language).