[Release gate] Complete exact-head acceptance for Unicode 18 benchmark identity profile

Current release-gate authority — 2026-09-23 KST

This issue gates the complete unicode-18.0.0-default-ignorable-exclusion controlled-benchmark stack. It is not a leaf-PR merge permit. Historical RED/repair detail remains in PR/issue history; this body is the current acceptance surface.

External provenance

Retained Unicode 18.0.0 receipt:

DerivedCoreProperties.txt: 1,159,889 bytes;
raw SHA-256 09c928886a178fcafd93c29e4bd59073a058e5a100b716d425cb563ab50f68c9;
Default_Ignorable_Code_Point: 27 source entries / 4,174 scalars;
ascending %06X\n normalization: 29,218 bytes;
normalized SHA-256 673264e62183e35f6055a2ad4940403e706669e0750fcc5d56a99f158fb3bb93.

Browser-issued WebDriver BiDi/Chromium identifiers remain outside this benchmark-owned grammar.

Current stack

protected main@87c4daa1830bac5a5228b6036752ad5633232085 → feat(core): enforce controlled benchmark acceptance thresholds #237 exact 4d175467c550c969d1ad22e51016473c0a4da034;
fix(core): reject bidi controls in benchmark evidence identity #322 exact a4c8ceaf67a075ef483334802aacfc54cf502068 still records predecessor feat(core): enforce controlled benchmark acceptance thresholds #237 base ea92c326...;
fix(core): version benchmark Unicode identity profile #324 exact 4e70d5ed9ce13f7b59012d39646e94ac41519c89 remains on fix(core): reject bidi controls in benchmark evidence identity #322 exact a4c8ceaf....

#237 is open / Ready / mergeable. #322 is open / Draft / mergeable and remains 11 ahead / 1 behind / diverged relative to current #237. #324 is open / Ready / mergeable and remains leaf-GREEN on its current exact head.

Delivery remains ancestor-first only: #237 current exact acceptance + normal protected integration → #322 ordinary/non-force adoption/adaptation + fresh exact-head acceptance/integration → #324 ordinary/non-force adoption + fresh exact-head acceptance/integration. Child evidence never transfers around an ancestor or to a restacked head.

#237 foundation gate

Predecessor ea92c326... executed native CI and exposed noncanonical rustfmt in the hostile control-character fixture plus uncovered ControlCharacterRunContext::Display. Ordinary-forward test-only exact 4d175467c550c969d1ad22e51016473c0a4da034 repairs both without changing production semantics or thresholds.

Current exact-head evidence:

MV3 35689677725: success;
CI 35689677783: success;
- Production coverage 106623791231: success;
- Rust contracts 106623791494: success;
SAST 35689677835: success;
Security 35689677811: success;
Noema review PRR_kwDOTulPlM8AAAABOoVPNA: APPROVED on exact 4d175467... at 2026-09-22 10:23:41 UTC;
review threads: 0;
CodeQL 35689677975: terminal failure, with no proved OriginWeave source/SARIF finding.

CodeQL detail: Detect 106623791602 succeeded. Python 106663165098, JavaScript/TypeScript 106663165121, and Actions 106663165232 reached the verdict contract and failed closed while authenticated codeql-dispatch/<language> statuses were absent. Coordinator 106704274687 later revalidated the exact #237 head/base, bound the three failed job IDs, obtained OIDC/repository-scoped App-token authority and successfully dispatched codeql-scan.

That dispatch is central producer .github run 35729253661 for exact OriginWeave#237@4d175467.../87c4daa.../35689677975. validate-dispatch 106750442061 is terminal SUCCESS, including App-token exchange and live target-PR metadata binding. The producer then created three language scan jobs — Actions 106824378689, Python 106824378827, JavaScript/TypeScript 106824378910 — and all three remain pre-step queued with runner_id=0, empty runner name and steps=[]. The current .github#712 boundary is therefore per-language hosted-runner admission, not producer validation. Exact updated specimen is recorded in .github#712 comment 5779826716.

Cross-repository terminal receipt publication/final settlement remains separately owned by .github#1929; its canary has independently proved HTTP 403 Resource not accessible by integration can occur when publishing target codeql-dispatch/* statuses even after real scanners execute. Thus #237 has repository/browser/security GREEN plus current-head counted approval/thread satisfaction but remains not merge-accepted until all three exact language scanners execute authentically and target-repository CodeQL receipts settle the failed leaf jobs under the canonical owner path.

#322 successor gate

Exact a4c8ceaf... remains Draft. Its current source already covers the broadened control-character diagnostic through the Bidi/line-separator contract, so the #237 repair must be adapted rather than blindly copied. Foundation order still requires #237 to land first; then #322 must ordinary/non-force adopt the protected generation, preserve all valid child commits, and reacquire all current-head evidence.

#324 leaf state

Exact 4e70d5ed9ce13f7b59012d39646e94ac41519c89 remains leaf-GREEN:

CI 35629802868: success;
Rust contracts 106432962452: success;
Production coverage 106432962080: success with exact owned-production function/line/region/branch enforcement;
MV3 35629802889: success;
current-head CodeRabbit advisory review: no blocking issue in the requested isolation/TRACEABILITY scope.

The two-sided regression proves valid expected / hostile observed and hostile expected / valid observed across all 4,174 DICP scalars. This evidence is valid only for the current leaf and becomes predecessor evidence after restack.

Buyer-facing baseline owner

#238 is the canonical documentation lane on protected base 87c4daa..., exact 7e94fe424bbf577058197f7d718fa5f715dd88ff, open / Ready / mergeable.

Its predecessor exposed a false-negative ordering oracle; current 7e94fe42... scopes stack-order validation to the Delivery remains clause. Current exact-head evidence:

CI 35689421774: success;
- Rust contracts 106623040891: success;
- Production coverage 106623041104: success;
SAST 35689421862: success;
Security 35689421820: success;
CodeQL 35689421861: run-level queued/nonterminal;
current-head CodeRabbit focused review: no actionable issue;
no qualifying current-head counted formal approval; author pending review untouched; no unresolved review thread.

For #238 CodeQL, Detect 106662259551 is SUCCESS. Actions 106694680527, Python 106694680572, and JavaScript/TypeScript 106694680626 all received runners and failed closed only after successfully reading the missing current-head verdict. Coordinator 106751338259 is now terminal SUCCESS and actually dispatched the exact current-head scan. That dispatch materialized central .github producer 35750892702, named for exact OriginWeave#238@7e94fe42.../87c4daa.../35689421861. Its validate-dispatch job 106824400524 remains pre-step queued with runner_id=0 and steps=[]. The #238 blocker therefore moved from leaf coordinator admission to central producer validation admission under .github#712; exact updated specimen is comment 5779880236. If that producer executes, .github#1929 remains the separate terminal status-publication/settlement boundary.

Thus #238 has native CI/SAST/Security GREEN and a successful dispatch coordinator but is not merge-accepted; its live producer must not be replaced with blind reruns or a source-neutral wake.

Remaining acceptance

Keep this issue open until the complete stack, or verified ordinary-forward successors carrying every valid delta, satisfies:

feat(core): enforce controlled benchmark acceptance thresholds #237 central producer 35729253661 admits and executes the exact three language scan jobs through .github#712, then .github#1929 proves terminal target-repository codeql-dispatch/* publication plus exact failed-job settlement on unchanged head; recheck the active ruleset, then integrate normally.
fix(core): reject bidi controls in benchmark evidence identity #322 ordinary/non-force adopts/adapts protected feat(core): enforce controlled benchmark acceptance thresholds #237, reacquires all exact-head evidence, then integrates normally.
fix(core): version benchmark Unicode identity profile #324 ordinary/non-force adopts protected fix(core): reject bidi controls in benchmark evidence identity #322, reacquires repository/browser/security/review/rules evidence including exact owned-production coverage, then integrates normally.
docs: refresh live product gap baseline #238 central producer 35750892702 clears authentic validation/scanner admission, its CodeQL owner path reaches terminal target-receipt settlement, and current review/rules/thread requirements are satisfied.
Final protected-main and release inventory reads confirm the expected signed head and immutable version/tag/package/SBOM/provenance/reproducibility/rollback state before any release claim.

If an executable failure appears, repair causal source/configuration through its canonical owner rather than manufacturing a wake, weakening a gate, synthesizing status, or copying owner logic. No self-approval, bypass, force push, destructive rebase, protected merge, tag, package publication, or immutable release is authorized by the current state.

2026-09-17 KST fresh publication-state check: one publication condition has changed, but the gate remains closed.

Primary-source state now:

https://www.unicode.org/Public/18.0.0/ucd/DerivedCoreProperties.txt is directly available at the versioned path rather than resolving through /Public/draft/. This is a real transition from the previous observation.
The returned file is still DerivedCoreProperties-18.0.0.txt, dated 2026-08-07, 16:19:42 GMT. Its Default_Ignorable_Code_Point section still totals 4,174 code points, so the observed versioned artifact is semantically consistent with fix(core): version benchmark Unicode identity profile #324's current table at this checkpoint.
However, the canonical https://www.unicode.org/versions/Unicode18.0.0/ page still says STATUS: This is a preliminary draft page for an upcoming release, and its UCD section still describes the data in beta-review/draft terms. The same page carries the date 2026 September 16, but the calendar/date label is not sufficient to override those explicit publication-state markers.

Therefore final Unicode 18.0.0 UCD provenance is still not established under this issue's artifact-driven acceptance rule. Do not promote #324's 2026-08-07 table to immutable/final provenance yet, even though the versioned path has stopped redirecting and the observed DICP scalar count remains 4,174.

The remaining promotion condition is now narrower: wait until the canonical Unicode 18.0.0 release surface no longer identifies itself as preliminary/draft (and no longer characterizes the UCD as beta-review draft data). Then capture the immutable final receipt: resolved URL, header/date, byte length, full-file SHA-256, DICP source-entry/scalar counts, exact ranges/code points, and normalized-property digest. Compare that receipt against #324 before deciding equivalence versus a fresh profile identity. Until then #324 remains Draft; no source-table rewrite is justified by the current observation.

Additional provenance observation from the same 2026-09-20 revalidation: the retrieval surface for the versioned DICP request reports a redirect to /Public/draft/ and returns a cached body whose header is DerivedCoreProperties-18.0.0.txt / Date: 2026-05-12, 22:09:55 GMT, while the current /Public/draft/ucd/ directory index reports DerivedCoreProperties.txt modified on 2026-08-07. The DICP section in that returned body still has exactly 27 source entries / 4,174 scalars, and independently expanding those 27 entries reproduces the existing 29,218-byte %06X\n normalized stream and SHA-256 673264e62183e35f6055a2ad4940403e706669e0750fcc5d56a99f158fb3bb93. This metadata mismatch is another reason not to manufacture a raw-file receipt from a draft/cached response. Keep the immutable-file gate open until stable versioned bytes can be fetched and hashed directly.

2026-09-21 revalidation: the immutable-artifact gate remains open. The official versioned DerivedCoreProperties.txt URL still resolves into /Public/draft/ucd/DerivedCoreProperties.txt; the current DICP section remains 27 entries / 4,174 scalars and still matches #324's 17 compressed ranges, so no semantic-table mismatch is established.

One additional currentness delta belongs to #324 before promotion: production rustdoc on is_unicode_18_default_ignorable currently says these are the scalars “published in Unicode 18.0.0 DerivedCoreProperties.txt.” That wording now overstates the artifact authority recorded by this issue. Repair it to distinguish the formally released Unicode 18.0.0 standard and the observed matching DICP property set from the still-unproven immutable raw-file identity. This is a rustdoc/provenance correction only; do not mutate the profile/table unless the eventual immutable artifact comparison differs.

Current #324 executable acceptance is blocked at runner admission rather than by a newly observed OriginWeave source failure.

Exact #324 remains accdd2d194f21ae1444ccca5297ce6590bc5384e, Ready / mergeable. Two fresh sweeps reproduced the exact-head CI 35531334971 jobs Rust contracts and Production coverage as queued with runner_id=0, no runner identity, no executed steps; exact-head MV3 Compatibility 35531334972 has Pinned Chrome for Testing MV3 fixture in the same state. Preserve these exact-head runs as incomplete evidence; do not blind-rerun, add a source-neutral wake commit, or count the current-head CodeRabbit review as executable GREEN.

Fresh owner-path verification shows this is not an OriginWeave queue-health enrollment gap. The canonical .github queue-health implementation from #1150 is merged, and the #2241 successor enrollment merged into central main includes OriginWeave. The central scheduled queue-health run 35521156760 on .github/main@e6334e229581a918e2f22de18733b76fa65d7e71 is itself still queued on the second sweep. Central .github queued workflow inventory rose from 291 on the first sweep to 294 on the second, while OriginWeave remained at 17. I routed that observer-availability finding to canonical owner issue ContextualWisdomLab/.github#712 in comment 5752312664 rather than copying operational logic into OriginWeave.

Therefore #325 remains open. The Unicode 18 artifact/provenance portion stays satisfied; the remaining release gate is unchanged exact-head repository/browser/security acceptance once runner admission resumes or the canonical owner provides valid out-of-band evidence. No exact queue root cause is asserted from the current data alone.

Acceptance dependency update: #323 item 7 also requires the canonical buyer-facing docs/product-technical-gap-baseline.md to name the exact adopted Unicode version/profile and reversal/migration path. Fresh #238 exact aba6c3c052e80e59c97e52eff9b71d0a77b286a2 still carries the old pre-release row (#324@ddc46f5..., 2026-08-07 pre-release snapshot, wait-for-final-publication wording), so this is now a documentation-to-code currentness gap rather than an external Unicode blocker.

The repair is routed to the single-writer baseline owner #238 in comment 5752627850; #324 remains out of that file. Keep #325 open until that owner records stable Unicode 18.0.0 provenance/profile/migration truth and the existing exact-head executable/review/governance gates complete. The row must remain OPEN until protected integration; final-UCD provenance alone is not product shipment.

#238 buyer-baseline owner has now moved from handoff to an ordinary-forward source repair. Exact #238 head is f47ed08685fca01bf4217b0476f9babcaac3e0af, three commits ahead / zero behind predecessor aba6c3c052e80e59c97e52eff9b71d0a77b286a2, with an effective delta limited to the focused navigation regression, docs/product-technical-gap-baseline.md, and its TRACEABILITY. The current dated receipt is 2026-09-20 22:00 UTC (135 open PRs / 5 Ready-non-draft / 130 Draft / 19 open non-PR issues). Its Unicode row now names #324 exact accdd2d194f21ae1444ccca5297ce6590bc5384e, the stable raw DICP receipt and normalized 27-entry / 4,174-scalar receipt, queued exact workflows, and this #325 exact-head acceptance boundary. September 15 / September 9 receipts and the immutable historical dossier remain historical rather than being rewritten.

CodeRabbit run ee213629-8af9-48df-a42d-6800a65bdd96 reviewed the exact aba6c3... → f47ed086... three-path delta and produced no actionable comments. This does not close #325: #238 exact required workflows remain nonterminal, while #324 CI 35531334971 and MV3 35531334972 are still queued. No predecessor, review-bot, queued, or publication evidence is promoted to executable GREEN.

Acceptance authority update: #324's former runner-admission state has resolved into executable evidence and a bounded ordinary-forward repair.

Exact predecessor accdd2d194f21ae1444ccca5297ce6590bc5384e reached hosted execution. CI 35531334971 completed failure only because cargo fmt --all --check found formatting drift in the two Unicode benchmark test files; repository Python contracts passed before that point, so Rust tests/Clippy/rustdoc were skipped. The sibling Production coverage job completed success with the exact production function/line/region/branch gate, and Manifest V3 Compatibility 35531334972 completed success.

The hosted rustfmt diagnostic artifact was applied without semantic edits or history rewrite: 1348f798e7b19df21b0930be704b47f1e4fedb06 formats controlled_benchmark_unicode_18_default_ignorable.rs, and current successor b89b40351152abe6a9c15fffd67f785933f6e164 formats controlled_benchmark_run_context.rs. Fresh compare from accdd2d... is 2 ahead / 0 behind and exactly two test paths. Current #324 is Ready / mergeable at b89b403....

New exact-head runs are CI 35556275575 and Manifest V3 Compatibility 35556275524, both currently queued. The predecessor coverage/MV3 successes are retained as causal evidence only and do not transfer to b89b403.... Keep this release gate open for current-head repository contracts/tests/Clippy/rustdoc/coverage/browser/security plus review/ruleset acceptance, and for #238's independent buyer-baseline lane.

Release-gate review state has advanced on both owned lineages; executable gates have not.

fix(core): version benchmark Unicode identity profile #324 remains exact b89b40351152abe6a9c15fffd67f785933f6e164, Ready / mergeable. Current-head CodeRabbit completion comment 5754855645 reports no blocking issue in the ordinary-forward hosted-rustfmt repair and confirms the successor delta is confined to the two benchmark test files. This supersedes the issue body's older statement that only predecessor review evidence existed. It is not a ruleset approval or executable GREEN. CI 35556275575 and MV3 35556275524 remain queued.
docs: refresh live product gap baseline #238 remains exact ce8fcb925d9c268972f0e1c16c01f0478a92f00c, Ready / mergeable. CodeRabbit run b659e3a5-e77d-4628-a865-1330a65b4030 reviewed the bounded three-path buyer-baseline delta and produced no actionable comments; all returned review threads are resolved. This likewise is not the required approving review. CI 35559887314, Security Scan 35559887283, CodeQL 35559887296 remain queued and SAST 35559887291 pending.

Keep #325 open. The remaining acceptance is now dominated by current-head executable/ruleset evidence and normal protected integration, not by an unreviewed source delta.

#238 buyer/documentation owner moved ordinary-forward from ce8fcb925d9c268972f0e1c16c01f0478a92f00c to exact 548fc0bc73489c1604fd09f48fbd3457f3d8f411 after a valid documentation-currentness repair. The new delta corrects ADR 0016 provenance: the in-memory originweave-bap lifecycle kernel is already protected-main implementation via merged #208, while ADR 0016 deliberately remains Proposed until an explicit policy-compliant lifecycle transition. Test-first head 23ee9f5567e3cf67a02030e427f881d25f99a1fb rejected the obsolete active-branch/non-protected-main claims; the current head repairs both indexes and the ADR without changing production runtime or Unicode semantics.

This supersedes #325's body reference to #238 ce8fcb... for current acceptance only; historical 04:07 UTC inventory/Unicode receipt remains historical evidence. Fresh 548fc0bc... workflows are CI 35587456757 queued, SAST 35587456646 pending, Security Scan 35587456656 queued, CodeQL 35587456648 queued. Predecessor review/check results do not transfer. Keep #325 open until #324 and the current #238 lineage both reach terminal exact-head acceptance.

Fresh buyer-facing prerequisite update (2026-09-22 KST): #238 has advanced ordinary-forward from 548fc0bc73489c1604fd09f48fbd3457f3d8f411 to exact 6bcf2b190bb414866f04f565e7cd9d7eb398b4c5 after a real hosted RED. CI 35587456757 completed failure only because Rust-contract job 106293995727 found one brittle navigation assertion: the contract expected #309 is merged into the #238 documentation lineage, while the canonical traceability says #309 remains merged into the #238 documentation lineage and records the same verified successor/adoption facts. Production coverage job 106293995521 on the predecessor succeeded. The test-only ordinary-forward repair 6bcf2b190... aligns the exact assertion with the current traceability wording without changing the dated receipt, production/runtime source, owner boundary, or acceptance semantics. Fresh exact-head runs are CI 35636623944 queued, Security Scan 35636623979 queued, SAST 35636623962 queued, CodeQL 35636623931 pending. Therefore #325 acceptance item 4 now refers to #238 exact 6bcf2b190...; predecessor coverage success does not transfer, and no #238 integration is accepted until the new exact generation reaches terminal required checks/review/ruleset satisfaction.

#238 buyer-baseline dependency is now exact 305c9f49c6b610240175b372910ea7312e430283 on unchanged protected base 87c4daa1830bac5a5228b6036752ad5633232085; the issue body’s f18272d... pointer is historical.

The ordinary-forward BAP provenance lineage remains f18272d... semantic-provenance repair → test-first 7ba2f58db0608e7dd3fea05bfbc31dd61654ba51 hostile marker-order RED → 305c9f49... ordered-marker causal fix. The current fix is still test-only: bounded_section() now requires its end marker to occur after the requested start marker, preventing a section-scoped assertion from silently consuming the rest of a document when the only matching end marker precedes the start. No production/browser/runtime/workflow/ruleset/dependency/release surface changed.

Fresh independent CodeRabbit review has completed on exact 305c9f49... and reports no actionable issue in this repair. That review does not transfer executable acceptance or constitute counted approval.

#238 exact-head execution remains incomplete: CI 35648156151, Security Scan 35648156008, SAST Semgrep 35648156012, and CodeQL PR 35648155834 are nonterminal. CI jobs Rust contracts 106493630016 and Production coverage 106493632291 are still queued, runner_id=0, empty runner identity, steps=[]. Therefore #325 acceptance item 4 is now bound to 305c9f49... and remains open until terminal required workflows plus current-head review/thread/ruleset satisfaction are independently established. No predecessor GREEN transfers, and no blind rerun/source-neutral wake is authorized by this state.

Material leaf-state transition on the controlled-benchmark stack: #324 exact 4e70d5ed9ce13f7b59012d39646e94ac41519c89 has now reached authentic runner-backed GREEN.

CI 35629802868: completed / success.
Rust contracts 106432962452: success; repository Python contracts, rustfmt, locked tests, strict Clippy, and API documentation all completed successfully.
Production coverage 106432962080: success; production function/line/region/branch measurement and exact coverage enforcement completed successfully.
Manifest V3 Compatibility 35629802889: completed / success.
The requested independent CodeRabbit review on this same exact head is also complete with no blocking issue in scope.

#324's PR body has been currentized to record these terminal receipts. This does not make the stack integrable around its ancestors: #237 and #322 remain prerequisites, and any future #324 adoption/restack creates a new exact head requiring fresh evidence.

Because runner admission has materially resumed for this exact OriginWeave lane, I moved foundation PR #237 from Draft to Ready to reacquire authentic current-head execution rather than waking source. That transition generated fresh CI 35655234587 and MV3 35655234482. A targeted retry of the formerly cancelled exact-head CI overlapped that transition: the fresh CI generation cancelled pre-execution while the original exact-head CI 34901948426 moved to attempt 2; its Rust-contract job 106517181140 is currently queued. The fresh MV3 generation remains queued. No source failure is inferred from that overlap, and I am not issuing another retry while an exact-head attempt is live. #237's historical CodeQL failure remains separately owned by the still-open canonical .github#1929 terminal-publication gap; it is not being blindly rerun here.

Issue #325 therefore stays open. The leaf now has present-head executable/review evidence, while ancestor-first acceptance and subsequent non-force adoption/revalidation remain mandatory.

Fresh release-gate authority update for the current OriginWeave controlled-benchmark stack:

fix(core): version benchmark Unicode identity profile #324 remains exact 4e70d5ed9ce13f7b59012d39646e94ac41519c89 on fix(core): reject bidi controls in benchmark evidence identity #322 a4c8ceaf67a075ef483334802aacfc54cf502068. Its exact CI 35629802868 and Manifest V3 Compatibility 35629802889 are terminal success, and the requested current-head CodeRabbit review reports no blocking issue in the expected-side isolation/TRACEABILITY scope. This is leaf exact-head evidence only; it does not transfer around feat(core): enforce controlled benchmark acceptance thresholds #237/fix(core): reject bidi controls in benchmark evidence identity #322 or across a future fix(core): version benchmark Unicode identity profile #324 restack.
feat(core): enforce controlled benchmark acceptance thresholds #237 is Ready at exact ea92c326e2dc4e3daa869aff1266c10b05453e7d, but foundation acceptance is still incomplete: fresh MV3 35655234482 remains queued; fresh CI 35655234587 cancelled pre-execution while original exact-head CI 34901948426 remains live/queued. Security 34901858754 and SAST 34901858842 are historical exact-head success, while CodeQL 34901858973 remains the central dispatch/verdict publication failure already handed to .github#712 / .github#1929. Do not add another blind retry while an exact-head attempt is live.
docs: refresh live product gap baseline #238's buyer-facing Unicode row was materially stale: it still named fix(core): version benchmark Unicode identity profile #324 b89b403... and queued CI/MV3. Ordinary-forward 11f6cc87d44e433ff051f5388ade815081450be9 → aaee73f175e868a6cc155efe5f9d059b21168468 → 26ccf2f72289ff266e14416ab7c0385c088413f9 currentized the buyer row/TRACEABILITY while preserving the dated 2026-09-21 04:07 UTC receipt and immutable historical dossier.
CodeRabbit review 5768176171 found the current Unicode/stack claims were regression-bound only in the buyer baseline. d1863803c0c1f8747da39183a22f16b121aa1b4b bound TRACEABILITY too, but review 5768232850 correctly found four full explanatory clauses overly prose-coupled.
docs: refresh live product gap baseline #238 current exact is 433c0df800ceeef7b4ffe356f816d04784905aa2. It keeps exact assertions for fix(core): version benchmark Unicode identity profile #324 SHA/run IDs/two-sided 4,174-scalar evidence/advisory-review marker, then semantically verifies the unique Delivery remains relationship with ordered #237 < #322 < #324 and separate ordinary/non-force, fresh exact-head, new exact head, and new evidence markers. Current-head CodeRabbit review 5768254670 reports no actionable issue in this focused semantic repair and confirms git diff --check clean. This advisory review is not a counted human approval.
docs: refresh live product gap baseline #238 exact-head workflows are now materialized but nonterminal: CI 35661512150 queued, Security 35661512032 queued, SAST 35661512055 queued, CodeQL 35661512013 pending. CI jobs Production coverage 106537603759 and Rust contracts 106537603815 are queued with no executed steps. No predecessor docs: refresh live product gap baseline #238 execution evidence transfers.

Keep this issue open. The release order is unchanged: #237 exact acceptance and normal protected integration → #322 ordinary/non-force parent adoption plus fresh exact-head acceptance/integration → #324 ordinary/non-force parent adoption plus fresh exact-head acceptance/integration. #238 exact 433c0df8... must independently satisfy its current-head workflows and review/thread/ruleset gates before buyer documentation can integrate. No child GREEN, advisory review, predecessor run, queued/pending run, or historical receipt is sufficient to collapse those boundaries.

Release-gate authority update — 2026-09-22 KST.

The issue body contains older execution/documentation generations; this comment supersedes those volatile sections without deleting historical evidence.

fix(core): version benchmark Unicode identity profile #324 remains exact 4e70d5ed9ce13f7b59012d39646e94ac41519c89, Ready / mergeable on fix(core): reject bidi controls in benchmark evidence identity #322 a4c8ceaf..., with exact CI 35629802868 and Manifest V3 35629802889 terminal success. Rust contracts 106432962452 and Production coverage 106432962080 are terminal success. Current-head CodeRabbit review found no blocking issue in the requested two-sided Unicode/TRACEABILITY scope. This leaf GREEN still cannot cross feat(core): enforce controlled benchmark acceptance thresholds #237/fix(core): reject bidi controls in benchmark evidence identity #322 or a future restack.
feat(core): enforce controlled benchmark acceptance thresholds #237 remains exact ea92c326e2dc4e3daa869aff1266c10b05453e7d, now Ready / mergeable but not accepted. Manifest V3 35655234482 remains queued; Ready-triggered CI 35655234587 is cancelled pre-execution and original CI 34901948426 remains queued. Security 34901858754 and SAST 34901858842 are success; CodeQL 34901858973 remains the separately-owned central terminal-verdict publication/wake failure. Do not blind-rerun while an exact-head attempt remains live.
fix(core): reject bidi controls in benchmark evidence identity #322 remains exact a4c8ceaf67a075ef483334802aacfc54cf502068, Draft / mergeable, without runner-backed current-head repository/coverage/browser acceptance.
Canonical buyer-baseline owner docs: refresh live product gap baseline #238 has advanced ordinary-forward to 7708d0bece87c4122a400f1aeb76cd66105d1502, Ready / mergeable. The only new delta scopes the stack-semantic TRACEABILITY regression to the unique current ## Decision section so retained historical Delivery remains prose cannot shadow the live authority. Fresh docs: refresh live product gap baseline #238 runs are CI 35663134130, Security 35663134037, SAST 35663134171, and CodeQL 35663134007, all currently queued; Rust contracts 106542781409 and Production coverage 106542781662 have no executed steps. Focused current-head review was requested in docs: refresh live product gap baseline #238 comment 5768436305.

Acceptance order is unchanged: #237 exact acceptance + normal protected integration → #322 ordinary/non-force adoption and fresh exact-head acceptance/integration → #324 ordinary/non-force adoption and fresh exact-head acceptance/integration, while #238 independently reaches terminal current-head documentation/review/ruleset acceptance. No predecessor or pre-restack evidence transfers.

Release-gate authority update: canonical #238 moved ordinary-forward from 7708d0bece87c4122a400f1aeb76cd66105d1502 to exact c7256482beeac84b69d98ef0826eae4da87166cb.

The new delta is test-only and closes a current-vs-historical evidence-oracle gap in tests/test_product_gap_baseline_navigation_contract.py: current Unicode #324 exact-head/run/review markers must now occur inside the exact ## Decision → ## Historical-evidence boundary section, rather than anywhere in TRACEABILITY where preserved historical evidence could mask stale current authority. Exact section headings are also matched as complete lines rather than substrings. Product/runtime/docs/workflow/ruleset/dependency semantics are unchanged.

Fresh #238 runs are CI 35665848563, Security Scan 35665848557, SAST Semgrep 35665848608, and CodeQL PR 35665848577, all queued. CI jobs Production coverage 106551317754 and Rust contracts 106551318049 remain runner-unassigned with steps=[]. Predecessor 7708d0be... execution/review evidence therefore does not transfer. Current-head CodeRabbit review was requested in #238 comment 5768731175.

Acceptance item #323.7 should now bind #238 exact c7256482...; ancestor-first #237 → #322 → #324 ordering and all evidence non-transfer/restack rules remain unchanged.

Current buyer-baseline dependency update (2026-09-22 KST): #238 has advanced ordinary-forward from c7256482beeac84b69d98ef0826eae4da87166cb to exact ed9675cd752936ccf490f7488bfcef6103fb41f2 on unchanged protected base 87c4daa1830bac5a5228b6036752ad5633232085.

The new delta is test-only and closes the buyer-surface half of the same historical-shadow class already repaired in TRACEABILITY. test_current_unicode_row_tracks_stable_publication_and_exact_candidate previously searched the entire current baseline for #324 exact head, Unicode publication receipts, CI/MV3 run IDs, two-sided validation markers, review result, and terminal-execution wording. A stale Unicode buyer row could therefore pass if those markers survived elsewhere in the current baseline. ed9675cd... adds a unique markdown-row selector keyed by the stable Unicode buyer-gap label, requires the complete exact evidence set inside that row, and adds an adversarial unit fixture proving an exact #324 SHA retained outside the row cannot satisfy the row contract. Compare from c7256482...: one commit, one test file, +51/-19, 0 behind. Production/browser/runtime/docs/workflows/rulesets/dependencies/releases are unchanged.

Fresh exact-head workflows are CI 35670469366, Security Scan 35670469367, SAST Semgrep 35670469317, and CodeQL PR 35670469361; all are currently nonterminal/queued. Current-head CodeRabbit review was requested in #238 comment 5769344397 and must materialize independently. No predecessor workflow/review result transfers.

Acceptance item 4 of this issue is therefore now bound to #238 exact ed9675cd.... #324 remains leaf-GREEN at 4e70d5ed..., but the controlled-benchmark order remains #237 acceptance/protected integration → #322 ordinary/non-force adoption and fresh acceptance/integration → #324 ordinary/non-force adoption and fresh acceptance. Keep this issue open; no blind rerun, source-neutral wake, force update, self-approval, gate weakening, merge, tag, publish, or release is justified by this change.

#238 acceptance authority advanced ordinary-forward from ed9675cd752936ccf490f7488bfcef6103fb41f2 to exact 0fcef6a361d5cb6709e3de7a50a4a3728e5c9784 on protected main@87c4daa1830bac5a5228b6036752ad5633232085.

The delta is test-only: tests/test_product_gap_baseline_navigation_contract.py now bounds the dated 2026-09-21 04:07 UTC observation receipt by exact ordered headings (Observed delivery cut → Buyer gap matrix) and adds an adversarial fixture proving a queue marker retained only in a later section cannot satisfy the receipt contract. Production/browser source, baseline prose, workflow source, rulesets and dependencies are unchanged.

Fresh exact-head runs are CI 35678067368, Security 35678067367, SAST 35678067262, CodeQL 35678067228; all are currently nonterminal. CI jobs 106588700017 (Production coverage) and 106588700208 (Rust contracts) are queued with no executed steps/runner identity. Predecessor workflow/review evidence does not transfer. Current-head CodeRabbit review was requested in #238 comment 5770191872.

Controlled-benchmark integration order remains #237 → #322 → #324. #324 leaf GREEN remains non-transferable across ancestor integration/restack. #238 must reach terminal exact-head workflows plus current review/thread/ruleset satisfaction before it can serve as accepted buyer-baseline evidence.

Release-gate authority update.

Two previously nonterminal gates produced executable findings and now have ordinary-forward repairs:

feat(core): enforce controlled benchmark acceptance thresholds #237 predecessor ea92c326e2dc4e3daa869aff1266c10b05453e7d: CI 35655234587 attempt 2 completed failure. Rust contracts 106591222760 failed canonical rustfmt; Production coverage 106591222543 failed exact 100% enforcement at 4,693/4,695 lines and 5,647/5,650 regions. The only uncovered production lines were controlled_benchmark.rs:492-493, the ControlCharacterRunContext Display arm. feat(core): enforce controlled benchmark acceptance thresholds #237 is now exact 4d175467c550c969d1ad22e51016473c0a4da034, one ordinary-forward test-only commit that applies the canonical rustfmt shape and exercises the deterministic error-message contract. Fresh MV3/CI/Security/SAST/CodeQL runs (35689677725 / 35689677783 / 35689677811 / 35689677835 / 35689677975) are queued; predecessor evidence does not transfer.
docs: refresh live product gap baseline #238 predecessor 5c299ab09f3b3be5098edd11a5e4fd27d5e651f3: CI 35678751637 completed failure from a test-oracle false negative. The Delivery remains line contains an earlier contextual #324, so whole-line index("#324") compared the wrong occurrence. Production coverage passed. docs: refresh live product gap baseline #238 is now exact 7e94fe424bbf577058197f7d718fa5f715dd88ff, one ordinary-forward +1/-1 test-only commit that scopes ordering checks to the actual Delivery remains clause. Fresh CI/Security/SAST/CodeQL (35689421774 / 35689421820 / 35689421862 / 35689421861) are nonterminal; predecessor evidence does not transfer.

The release order remains unchanged: #237 exact acceptance and protected integration → #322 ordinary/non-force adoption plus fresh acceptance/integration → #324 ordinary/non-force adoption plus fresh acceptance/integration. #324's prior leaf GREEN is predecessor evidence only after its future restack. Keep this issue open; no protected merge/tag/package/release claim is authorized by these new heads.

Navigation Menu

Repository navigation

[Release gate] Complete exact-head acceptance for Unicode 18 benchmark identity profile #325

Current release-gate authority — 2026-09-23 KST

External provenance

Current stack

#237 foundation gate

#322 successor gate

#324 leaf state

Buyer-facing baseline owner

Remaining acceptance

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Release gate] Complete exact-head acceptance for Unicode 18 benchmark identity profile #325

Description

Current release-gate authority — 2026-09-23 KST

External provenance

Current stack

#237 foundation gate

#322 successor gate

#324 leaf state

Buyer-facing baseline owner

Remaining acceptance

Activity

seonghobae commented on Sep 15, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 21, 2026

seonghobae commented on Sep 22, 2026

seonghobae commented on Sep 22, 2026

seonghobae commented on Sep 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions