Repository navigation
Conversation
Add one early navigation paragraph to the current four-file start section and Quickstart. Preserve all existing proof, media and history text. Co-authored-by: Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Scaffold Handoff — For Your Coding Agent
Immutability CheckMode: advisory ✅ No immutable files were modified in this branch. Changed Files
Needs Adversarial Review — Do NOT Apply YetThese proposals passed the reject check but have not been approved by
Safety Boundary
Immutable files (never modify):
Scaffold files (safe to modify):
|
HomenShum
changed the title
HomenShum
changed the title
This was referenced Oct 10, 2026
Resolve DOMPurify 3.4.17 within the existing Mermaid range. Preserve all other lock records, including the reviewed Undici repair, and append the measured audit reduction, successful build and unchanged stale-proof failure.
This branch was successfully deployed
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
1 participant
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.
Developers and coding agents get a clear onboarding entry and patched compatible dependencies without changing NodeRoom's runtime or release gates. This PR retains the direct Undici 8.11.2 repair and updates the locked DOMPurify sanitizer from 3.4.14 to 3.4.17 within Mermaid's existing supported range. The repository changelog preserves the before/after evidence and remaining failures.
The new sanitizer follow-up changes only three lock fields and appends the changelog. All 1,078 other lock records remain identical to the previous PR head
c8789df42a425f6d101ecfac8e29a0cfa4b06eb9, including both Undici versions. Manifests, README, application code, tests and proof assets are unchanged by this follow-up.Local evidence on Node 22.22.2:
Release remains blocked by authentic fresh-user proof and the full required gates. No timestamp, freshness policy, claim, checker or CI condition was relaxed. The low KaTeX chain remains: its patched release is outside the current incoming ranges, so a broader renderer migration is separate work. No forced override or dependency suppression was added.
Earlier failed executions remain in history and in
CHANGELOG/qa/production-gate.md; this amendment does not make them pass. Exact follow-up identity, independent review and natural CI results will be appended after publication. No merge, production deployment, application model call or paid evaluation is claimed.Follow-up candidate:
fa5c3df1ea750c9c0c7db0d6a0ab14cfbba29f83, treef159b0761ec88cb2e408b9b10a310662d8c71b7d, sole parentc8789df42a425f6d101ecfac8e29a0cfa4b06eb9. Independent code and simplification reviews approve this exact two-file amendment for PR publication only; the review independently verified the registry tarball digest. Its direct commit-area check passes. Natural CI is pending; merge remains blocked.Natural CI for
fa5c3df1is now FAILED in both PR verify and push verify. Both ordinary lifecycle-enabled installs succeed and report 17 all-dependency findings (10 low, 4 moderate, 3 high). Their production-only audits report 10 low findings and clear the unchanged moderate threshold; subsequent checks proceed untilproofs:stalenessrejects the same 45.6-day-old receipt against its 30-day window. Later production-gate steps remain unreached. The exact direct push passes its two-area commit-message check. No gate was bypassed and this PR remains unmerged.