fix(deps): update fast-uri to clear the inherited security-audit failure

[mohanagy]

npm audit --audit-level=high fails on next's locked development dependency fast-uri 3.1.5. The same failure blocks documentation PR #742 and the separately validated retrieval fix in draft PR #747.

Evidence:

• First failure: run 33975026114, PR docs: align roadmap with focused stories and evidence limits #742 head 5af65b1fe236d4d548e21b975bc6c6364bee8213.
• Repeated failure: Ubuntu Node 22 job 101544190402, PR fix(retrieve): preserve helper source when file evidence wins #747 head e02dcfa0d8751cdaafe9de6154019c500282e63d. Tests and coverage passed; security audit failed. Five other CI lanes passed.
• Local read-only reproduction on that exact candidate: npm audit --package-lock-only --json --audit-level=high exits 1 with one high-severity package and the four advisories below.
• package.json and package-lock.json are byte-identical between base 72ecb4aa72899c5fa1ba4e2c27795070e74871eb and PR fix(retrieve): preserve helper source when file evidence wins #747. Lock SHA-256: 0144eb0ddf92f78c69f10089d0e0414485594966ff5be4f36f655c7aa5cff53e.

Dependency paths: root dev dependency ajv ^8.20.0 resolves to ajv 8.20.0, which requires fast-uri ^3.0.1; root dev dependency ajv-formats 3.0.1 also reaches that Ajv. All three lock entries are marked dev: true; this is dependency classification, not an exploitability claim.

Affected advisories:

• GHSA-5jgf-p345-68v8
• GHSA-f65p-4m7j-42xc
• GHSA-fph4-wmhf-6fwf
• GHSA-jqff-g426-hqxp

The live audit identifies affected 3.x ranges ending before 3.1.6; the npm registry confirms fast-uri 3.1.6 exists. A compatible targeted lockfile update is the first maintenance candidate, subject to validation.

Bounded implementation and acceptance:

• Codex CLI authors a separate maintenance PR into a freshly resolved next. Refresh the fast-uri lock entry within Ajv's existing range, and inspect the complete diff. No broad audit-fix upgrade, product code changes or audit suppression.
• Use a clean isolated checkout. Verify install, the dependency chain and npm audit --audit-level=high; run the existing qualification/schema validation that consumes Ajv and normal required CI.
• Require review of the exact final head and successful relevant CI. Preserve both original failed runs. This is the second occurrence of the existing CI signature, so repeating the unchanged failed lane is forbidden by the recorded CI policy.
• After separately authorized integration and post-merge validation, refresh fix(retrieve): preserve helper source when file evidence wins #747 and docs: align roadmap with focused stories and evidence limits #742 onto the fixed base and validate their resulting exact heads before considering integration.

This issue is separate from retrieval-source preservation, #710 timing/lifecycle maintenance and broader Madar quality qualification. Opening it does not authorize a model run, merge, release, or closure of #740.

[mohanagy]

Bounded #748 maintenance contract

Base: 72ecb4aa72899c5fa1ba4e2c27795070e74871eb (next, freshly fetched). Size: small, one lockfile entry, target under one working day. #748 is independent maintenance that blocks integration of #747/#742; their product/documentation changes remain separate. Their original failed CI runs are retained.

Defect and class: exact-base npm audit --package-lock-only --json --audit-level=high exits 1 for one locked package, fast-uri 3.1.5, and four advisories: GHSA-5jgf-p345-68v8, GHSA-f65p-4m7j-42xc, GHSA-fph4-wmhf-6fwf, GHSA-jqff-g426-hqxp. Both root development dependency paths (ajv directly, and ajv-formats through Ajv) converge on the single node_modules/fast-uri entry. All affected installed paths in this lockfile are enumerated by this class. Each authoritative advisory identifies 3.1.6 as its patched 3.x release; the npm registry confirms its tarball/integrity, unchanged license/funding and no declared dependency or engine addition.

Owner and source boundary: only package-lock.json, packages["node_modules/fast-uri"], and only its version/resolved/integrity fields may change. Preserve all other bytes, including dev: true, funding/license, root lock metadata, package.json, Ajv/ajv-formats entries, source/tests, workflows and qualification freeze files. Preserve Node20/22 and current npm lock format. No audit suppression, range widening, broad dependency upgrade, npm audit fix --force, product correction, new tests, corpus rerun or graph-quality claim.

Finite controls:

State	Required observation
Exact base3.1.5	Recorded audit fails with this four-advisory class.
Candidate3.1.6	Clean install resolves verified tarball/integrity; both Ajv paths resolve3.1.6; high-severity audit passes.
Unexpected changed lock entry/metadata	Complete diff/byte-preservation check rejects the candidate.
Version/URL/integrity disagree	Registry metadata and clean-install checks reject the candidate.
Lost dev classification or changed dependency range	Exact entry/root manifest invariants reject the candidate.
Valid/invalid qualification and registry examples	Existing Ajv consumers retain their acceptance/rejection behavior.

Validation in the isolated candidate with Node22.22.3:

npm ci --no-audit
npm ls fast-uri ajv ajv-formats --all
npm audit --audit-level=high
npm run qualify:validate
npm run test:run -- tests/unit/qualification-contract.test.ts tests/unit/mcp-registry-metadata.test.ts
git diff --check

Inspect the entire lockfile diff and verify all bytes outside the three admitted values are unchanged. These invariants are also the mutation controls: old version, wrong URL/integrity, and changed dev/range/outside-entry metadata must be rejected. No production test is added to assert a literal dependency version. The existing CI matrix then runs on all six OS/Node lanes; Ubuntu22 must pass the audit and reach its later eval steps. Local checks cannot substitute for CI. No unchanged rerun of the twice-failed audit signature.

Determinism/evidence: freeze exact base/tree, lockfile bytes, registry/advisory response bytes, runtime and prompt/launcher identities. A registry audit is time-dependent; retain timestamped original/final responses. No new performance threshold applies to this development-only dependency update; runtime code, measured runners and corpus inventories stay unchanged. Changed candidate bytes invalidate exact-head review/install/audit evidence. Moved next requires refreshing the base and rechecking scope before dispatch/integration. Reviewers receive exact source/diff/evidence packets, never predecessor verdicts or the manager's reasoning.

Prior art: all eight open PRs and current issue748 were checked; none supplies this fast-uri repair. The source-preservation PR changes only retrieve.ts and its regressions; neither it nor the documentation PR changes the inherited lockfile. The earlier two failed CI runs and current exact-base local reproduction demonstrate the same dependency defect. Reuse existing schema validators/tests; no new framework.

Execution: Codex CLI authors the minimal diff in one fresh, ChatGPT-authenticated, shell-disabled packet run. Root may apply only that returned diff mechanically. A separate fresh PREQUAL packet review precedes local candidate qualification; a third fresh FINAL packet review receives the resulting exact-head validation evidence. These are bounded packet reviews and do not imply the reviewers ran commands. Full PR CI is recorded separately. Root handles commands, Git and GitHub. No dedicated OpenAI API use.

Rollback: revert the single accepted dependency-lock commit, preserving failed/audit/review artifacts; doing so restores the known inherited audit failure. No destructive cleanup. No merge, release, tag or closure of #740 is authorized by this preparation.

Resources: propose an additional50,000 recorded CLI input tokens for one author plus two fresh reviews, shared with the existing2,217 remainder. This is a cumulative recorded-usage allowance with reactive stopping, not a hard in-flight bound or total account/billing measurement. No model run has begun. Missing usage, observed allowance exhaustion, a rejected scope, or an incomplete run stops subsequent dispatch; no silent retries or unlimited author loop. A worktree is created only when the model allowance is authorized, using the existing approved worktree location and exact base.

[mohanagy]

PR #749 is ready for the maintainer merge decision at 0c7c100630e962c25e687badd49197c3322d897b (tree c75872afcbe98fbed179388d9a9a9554ca44ec1a). Only the fast-uri lock entry's version/resolved/integrity values change, from 3.1.5 to 3.1.6; all other bytes are preserved.

Local clean install, both Ajv paths, zero-vulnerability audit, 21-file qualification freeze, 55 focused tests and clean/diff checks passed. Separate fresh CLI reviewers returned PREQUAL-GO and GO-748. CodeRabbit reviewed this head with no actionable findings. First CI run 34081270107 passed all six lanes, including the security audit and the later demo/eval gates on Ubuntu/Node 22. GitHub's test merge has the exact candidate tree. Local startup timeouts and their successful unchanged-command completion remain recorded.

CLI AUTHOR/PREQUAL/FINAL recorded 34,555 input tokens; cumulative 4,632,338 against the 4,650,000 ceiling, leaving 17,662 including carryover. All 3 permitted sessions are complete. Existing ChatGPT authentication was used; no dedicated API-account route.

This is the dependency-repair result. The demo's report-only grounded-match metric prints 116.7% and is not used as a quality claim. No merge or release has occurred. Keep #748 open until authorized integration and successful post-merge verification; #740 remains open, and PRs #742/#747 remain separate and blocked on that integration. The earlier failed CI runs and their signature history are retained.

[mohanagy]

PR #749 is merged into next as 1e64e752675e847abe861d3705b4eb49b553c9ed. Its tree is exactly the reviewed candidate tree; only the fast-uri lock entry changed to 3.1.6.

Post-merge CI run 34083400941, first attempt on that merge commit, passed all six OS/Node jobs. Each reports 321 passing test files. Ubuntu Node22 security audit reports zero vulnerabilities; coverage, packed retrieval parity and enforced demo evaluation also pass.

This completes #748 and removes the inherited dependency blocker. PR #747 will be refreshed and validated separately on this base; #740 remains open. The six CI jobs do not replace the historical product-quality evaluation. Original failures and exact-head author/review/CI evidence remain retained. No dedicated API call, credit purchase or reset was used.