docs: reconcile protected runtime and commercial gap authority - #547
Draft
seonghobae wants to merge 29 commits into
Draft
docs: reconcile protected runtime and commercial gap authority#547seonghobae wants to merge 29 commits into
seonghobae wants to merge 29 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
Canonical
docs/product-technical-gap-baseline.mdmust stay code-current while separating protected truth, active candidate, transient workflow observation and foreign-owner authority. #546 and its stacked consumers advanced again after a fresh exact-path identity repair, so the prior baseline became stale.Current reconciliation — 2026-09-06 KST
Documentation repair
af5fae8645ab6abe5b0faa02020d141b992e9cd8refreshes the baseline around live authority:main@e1ac9d50f6c646f04be8c137c8acdc7200182fcd;04376e279c61a7491cb311589b28dc643bf65837, retaining JSON-safe recovery and adding RED3328f7ba...→ production04376e27...for Linux leading-backslash Git path identity;52b9195bb9f5006ffcd2dca7dedbf05c51169239and fix(reviewer): bind failed checks to actionable source evidence #548 exactdd7353342b4776b007b74f8b223e172dcb3d4f4f, ordinary two-parent/non-force, 68/83 ahead and 0 behind exact fix(reviewer): fail closed on empty CodeGraph semantics #546;7e5ff9cd...is recorded as the durable Workflow/Task Execution candidate whose latest predecessor reached all tests before the 100% coverage gate exposed missing failure/authority branches;.github/main@7f4c5e3e...,.github#712,.github#1759);Current exact authority
af5fae8645ab6abe5b0faa02020d141b992e9cd8;ci 33979800984— pending/non-passing;reviewer-ci 33979801016— queued/non-passing;Security Scan 33979801035— queued/non-passing;patch-validator-image 33979801113— pending/non-passing;04376e279c61a7491cb311589b28dc643bf65837remains the repository-wide semantic-review prerequisite.Keep Draft until this unchanged exact head receives current CI/reviewer/Security/image and every applicable documentation/coverage/package/SBOM/vulnerability/provenance gate with zero valid unresolved findings. Do not promote active candidates into protected truth, self-approve, force-push/destructively rebase, or weaken documentation fitness gates.