fix(security): repair shared dependency scan failures

[seonghobae]

October 3, 2026 — reviewed owner successor; Draft, not merged

Current head 64eff330f2bf8e383c4de15cb7fc1a89063d1c85, parent aa08f2a6c63366df6f4109a74dbc759b23423541, reviewed36-path tree 84faeee48240a6b8b58c8b69931d31bc1cc600de and complete diffSHA256 ba036e3dea576c1677864d34db03907d5327cf39575c1990c611fe779c50fd59. Independent complete source verdict passed for safe Draft publication only. Ordinary same-branch push and remote/PRhead verified; no duplicate PR, forced push, protection bypass or counted self-approval.

Vite8.1.4 exact pnpm patch bounds embedded braces parser stack at64 and recursive compile/expand/stringify at65. Eight anchored vendor hunks reproduce35supplierfiles exactly. This is narrow recursion remediation, NOT embedded braces/chokidar removal, comprehensive DoS/resource protection or asynchronous watcher/process-survival assurance. Canonical package audit0 refers to external inventory only. Exact mandated regressions reject restored vulnerable bundle. Prior private-TMPDIR blocker fixed; actual file-subscription witness resolves reproduced premature-global-ready fixture race without sleeps, polling, retries or deadline increases.

Actual clean committed-head frozeninstall/normaldependency+watchcontracts/437frontendJUnit0fail0skip/lintmaxwarnings0/typecheck/productionbuild/audit0 all passed. Full backend1817passed33skipped. Committed-head production UI/mock collection across3projects completed naturally:177unique,158passed19unchangedskips,0unexpected/flaky. Original60s/15slimits, Node24.19.0/pnpm11.5.3/matchingChromium1243. The19skips include15live/model and4desktop-only conditions. UI/mock acceptance is not realbackend/providerexecution. Earlier timeouts/warnings/production-env failures remain separate failed historical evidence.

Separate private complete#1317af362d58 composition with previous runtime/frontsource reached freshPG17migration0020 and actual signedHttpOnly EMLimport/list/detail/lexicalsearch/other-owner isolation. Complete primary14API allHeaders guard passed; supplementary original initiated27request guard still rejects2canceledsearchcookieobservations/exit1. Separate actual Next ingress measured25received requests allcookiepresent/forbidden0/200, with explicitcancellation/CDP gaps. This is private integration, not standalone#1828freshbackend, protected release or provider/OIDC-admin acceptance. No generic canceled-request exemption or all-console-clean claim.

Exacthead failed hosted admission jobs observed: 11. Their current annotations are retained; checks/formalqualifyingreview/protectedmerge/releasedusability remain unmet. No auto-merge or gate waiver. KeepDraft and Issue#1428OPEN. Nonblocking source-review suggestions retained as follow-ups without modifying this frozen reviewed tree.

2026-10-01 current owner admission (authoritative)

• Exact owner head: 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2; base: develop@042b0c70531b229af3acbd0421a2f23098d848b3.
• This is the canonical repository-wide dependency/security owner: backend manifest+lock, frontend Next/sharp, executable pin contract, doctoring, CHANGELOG, and Gap baseline.
• Existing exact-head Application CI, Security, Bandit, SAST, and container build evidence is GREEN. Prior Draft CodeQL is skipped and is not acceptance evidence.
• Ready is review/check admission only. Fresh Ready-triggered Checks, independent approval, and ordinary merge remain mandatory.
• Partial Dependabot PRs build(deps): bump urllib3 from 2.7.0 to 2.8.0 in /backend #1834–build(deps): bump litellm from 1.89.2 to 1.93.2 #1843 remain evidence/delta sources and must not merge independently while the owner refresh is unresolved.

Summary

• centralize the repo-wide dependency findings inherited by Draft PRs JSON 포매터 도구 추가 #1824, 🎨 Palette: [UX improvement] #1825, and 🎨 Palette: [Network Graph UX improvement] #1827 in a dedicated develop-root owner change
• pin PyJWT 2.14.0, AnyIO 4.15.1, oauthlib 4.0.0, Next.js / eslint-config-next 16.3.6, and Sharp 0.35.4 across source manifests and generated locks
• upgrade Starlette to 1.7.0 and add HTTPX2 2.13.1 for its warning-clean TestClient path under AnyIO 4.15
• add a cross-lock regression contract and record exact run/job RCA plus owner-boundary guidance

Root cause

Protected develop@042b0c70531b229af3acbd0421a2f23098d848b3 still resolves the vulnerable shared versions. Partial fixes were mixed into unrelated stale PR heads, so each PR inherited a different subset of the same repository-wide scan failure. The first full warning-fatal validation also exposed Starlette 1.3.1's deprecated AnyIO alias; this change fixes that supplier boundary instead of suppressing the warning or downgrading AnyIO.

TDD and local evidence

• RED: the dependency contract observed PyJWT 2.13.0; after adding the Starlette contract it observed 1.3.1; after adding the TestClient backend contract HTTPX2 was absent
• GREEN: PYTHONWARNINGS=error imports starlette.testclient.TestClient successfully
• backend: 1,806 passed, 33 skipped with PYTHONWARNINGS=error; Ruff green; uv pip check green
• Python audit: no known vulnerabilities
• frontend: 51 files / 437 tests green; ESLint, TypeScript, Next.js 16.3.6 production build green
• pnpm production audit: no known vulnerabilities

Admission

This PR is Ready for independent review only. Exact-current-head required Checks and independent review must be terminal successful before ordinary merge. Pending, queued, skipped, or predecessor results are not treated as passing. No gate or advisory is suppressed.

Full traceability: docs/doctoring/2026-09-30-dependency-security-scan-rca.md.

Summary by CodeRabbit

• Security & Reliability
  • Updated backend dependencies, including PyJWT, Starlette, AnyIO, and urllib3, with matching lockfile updates.
  • Updated frontend Next.js and Sharp dependencies.
  • Improved compatibility across shared dependencies and removed duplicate ownership of packages between core and optional components.
• Bug Fixes
  • Corrected a JWKS test fixture so authentication data is parsed and verified as expected.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: ContextualWisdomLab/naruon/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: dc54f964-d078-4ae6-bfff-38319ce5f55b

📥 Commits

Reviewing files that changed from the base of the PR and between 042b0c7 and 74f9d6d.

⛔ Files ignored due to path filters (2)

• backend/uv.lock is excluded by !**/*.lock
• frontend/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (12)

• AGENTS.md
• CHANGELOG.md
• backend/pyproject.toml
• backend/requirements-agent.txt
• backend/requirements-hashes.txt
• backend/requirements.txt
• backend/tests/test_auth_real.py
• backend/tests/test_container_dependency_pin_contract.py
• docs/doctoring/2026-09-30-dependency-security-scan-rca.md
• docs/product-technical-gap-baseline.md
• frontend/package.json
• frontend/pnpm-workspace.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

Backend and frontend dependency pins and lock records are updated. Tests check dependency pins, lock ownership, and a populated JWKS response. Repository guidance and documentation record the security-scan handling and verification history.

Changes

Dependency Security and Lock Alignment

Layer / File(s)	Summary
Dependency pins, lockfiles, and parity contract backend/pyproject.toml, backend/requirements.txt, backend/requirements-hashes.txt, backend/requirements-agent.txt, frontend/package.json, frontend/pnpm-workspace.yaml, backend/tests/test_container_dependency_pin_contract.py	Backend pins and generated hash-lock records are updated, and shared package pins are removed from the optional agent requirements. Frontend Next.js, eslint-config-next, and Sharp versions are updated. The dependency contract checks backend pins, frontend lock resolutions, and disjoint package ownership between backend and optional agent requirements.
JWKS test fixture update backend/tests/test_auth_real.py	The fake JWKS response provides an RSA signing key, and the fetch assertion expects that key set.
Security-scan guidance and records AGENTS.md, CHANGELOG.md, docs/doctoring/2026-09-30-dependency-security-scan-rca.md, docs/product-technical-gap-baseline.md	Guidance describes handling repo-wide dependency findings. The changelog, RCA, and baseline record dependency updates, scan findings, test results, and integration conditions.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 74f9d

Dependency, lock, and fixture validation is reported as passing, and no actionable code issue remains from this review. Promotion remains subject to the stated independent-review condition.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 74f9d

The inspected changes preserve authentication and network destination controls and strengthen dependency ownership checks. No introduced security issue was established. Risk remains low rather than minimal because compatibility of the refreshed dependencies, particularly signing-key cache and recovery behavior, is not fully established.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — Potential dependency-compatibility effects extend beyond the edited fixtures to backend token verification and frontend framework consumers. The inspected changes do not establish new tenant privileges, additional network destinations or a newly reachable sensitive operation.

Trust Boundaries and Controls

• observed — The existing JWKS client connects only to addresses in the validated destination tuple while preserving the hostname for TLS identity and the HTTP Host header. It bounds response reads, rejects oversized and error responses, and closes each connection before caching a successfully parsed response. The changed test retains assertions for destination, hostname, Host header and successful connection cleanup.

Resilience and Maintainability Implications

• observed — The application retries the validated address list, raises after exhaustion and clears application signing keys when preload fails. The changed fixture exercises a single successful address and does not establish repeated-refresh, concurrent-refresh or inherited PyJWT cache behavior. These are compatibility coverage limits, not observed security regressions.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: repairing shared dependency scan failures.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Exact-head verification refresh for 222099a6b7433870e33e8149ec2bef0049f5f799:

• Security Scan run 36668747533: success
• SAST Semgrep run 36668747697: success
• Bandit run 36668747486: queued (security job 109738988419)
• Application CI run 36668747540: queued (backend job 109738989019, frontend job 109738989083)
• image validation run 36668747747: queued (three validation jobs)
• CodeQL PR run 36668747550: skipped because the PR remains Draft; this is explicitly not treated as passing

The remote commit contains the same 12-file tree (7e3f3343ab3e8239467dda5d5f1af35b127d333d) that passed local verification. Keep Draft until all required exact-head gates and independent review are terminal successful.

[seonghobae]

Consumer reproduction added for canonical-owner traceability:

• Consumer: 🎨 Palette: [Network Graph UX improvement] #1827 exact head 2b974f91e567a95f1c32eeb796c07d1c0f4dc2aa
• Security Scan run/job: 36671076900 / 109746024317
• Exact checkout identity matched the consumer head.
• Trivy gate reported 28 shared dependency findings: PyJWT 20 (requirements + uv lock), anyio 3, oauthlib 2, Next 2, sharp 1.

These are the same shared-manifest/lock families owned here; no duplicate leaf repair belongs in #1827. Acceptance remains: this owner PR reaches exact-head integrated GREEN and independent review, merges ordinarily into develop, then #1827 incorporates that released base delta without force-push and reruns all exact-head gates.

[seonghobae]

Exact consumer evidence: #1827

Draft #1827 exact head 2b974f91e567a95f1c32eeb796c07d1c0f4dc2aa reproduces the shared-base dependency defect in Security Scan run 36671076900 / job 109746024317. Trivy reports 28 findings spanning exactly the owner surfaces repaired here: PyJWT, AnyIO, oauthlib, Next.js, and Sharp across backend/requirements.txt, backend/uv.lock, and frontend/pnpm-lock.yaml.

At #1828 exact head 222099a6b7433870e33e8149ec2bef0049f5f799, Security Scan run 36668747533 and Semgrep run 36668747697 are terminal successful. Application CI, Bandit, and image build are still queued; CodeQL is skipped and is not represented as GREEN. The PR correctly remains Draft until every required exact-head gate and independent review are satisfied.

After protected integration, #1827 must merge the new protected develop head normally and generate new exact-head evidence.

[seonghobae]

Consumer evidence: #1818's exact head failed Trivy on the same shared AnyIO, Next.js, and Sharp locks. Its valid URL traversal delta is now non-force stacked on this canonical owner head 222099a6b7433870e33e8149ec2bef0049f5f799 via merge commit 56d42e00ebd734d9a5dfe6536b3050ca01963f82. The combined tree passed 1,809 backend tests with warnings fatal, 437 frontend tests, focused URL/cross-lock contracts, and both Python and pnpm production audits with no known vulnerabilities. Both PRs remain Draft pending exact-head hosted gates; this is consumer validation, not merge authorization.

[seonghobae]

Application CI RCA / owner repair

• 실패 증거: exact-head Application CI run 36668747540, backend job 109738989019
• 직접 원인: CI가 core/Noema hash lock을 한 resolver invocation으로 설치할 때 core의 httpx2==2.13.1 / httpcore2==2.13.1과 optional lock의 중복 2.5.0 핀이 충돌해 ResolutionImpossible이 발생했습니다.
• 최소 수선: requirements-agent.txt에서 core-owned packages를 제거해 core lock을 단일 버전·hash 권위로 만들었습니다. 경고 억제, 취약 버전 downgrade, gate 완화는 없습니다.
• RED→GREEN 계약: test_optional_agent_lock_does_not_redeclare_core_packages가 중복 핀에서 실패한 뒤 현재 통과합니다.
• 재현 검증: fresh Python 3.14 venv에서 CI와 동일한 pip install --require-hashes -r backend/requirements-hashes.txt -r backend/requirements-agent.txt가 성공했습니다.
• 회귀 검증: backend 1808 passed, 32 skipped (PYTHONWARNINGS=error), focused lock/Noema 21 passed, Ruff clean, git diff --check clean.
• RCA/상태/CHANGELOG를 같은 commit에 기록했습니다.

Repair commit: e725203385a6381040b22231281fc63d9ed09f62.

이 PR은 새 exact-head hosted Checks가 terminal successful이 될 때까지 Draft/Proposed 상태를 유지합니다. queued/skipped/predecessor 결과는 통과로 취급하지 않습니다.

[seonghobae]

2026-10-01 advisory refresh — canonical-owner repair

Exact consumer evidence from Draft #1833 at 940e9166650e81d68802180bef9c242c8f53471c:

• Security Scan run 36804726949
• dependency-review job 110186442561: PyJWT 2.14.0 / GHSA-42vr-xj54-vc7v
• Trivy job 110186442634: PyJWT CVE-2026-101918 and urllib3 2.7.0 CVE-2026-97687/97688/97689

Root cause: the prior owner head was valid against its then-current advisory set, but the exact-current consumer scan received newly published residual advisories. This remains a shared manifest/lock responsibility owned here, not a product-graph leaf fix.

Repair head: 2311edff3cc2c9546eeb7fda41ef8b8c67be5680

• RED: dependency parity contract required PyJWT 2.15.0 and urllib3 2.8.0 and failed against PyJWT 2.14.0.
• GREEN: source manifests, uv lock, and pip hash lock now agree on PyJWT 2.15.0 and urllib3 2.8.0; no unrelated dependency moved.
• focused contract: 2 passed
• full backend with PYTHONWARNINGS=error: 1,808 passed, 32 skipped
• fresh-cache pip-audit -r backend/requirements-hashes.txt: no known vulnerabilities
• git diff --check: clean
• RCA, CHANGELOG, and docs/product-technical-gap-baseline.md updated in the same commit

This PR remains Draft. New hosted exact-head Checks must be terminal successful; pending, queued, skipped, and predecessor results are not acceptance evidence.

[seonghobae]

Application CI follow-up repair

The refreshed dependency owner exposed one test-fixture incompatibility on exact head 2311edff3cc2c9546eeb7fda41ef8b8c67be5680:

• owner Application CI run 36805472113, backend job 110188721153
• consumer Application CI run 36805642399, backend job 110189254190
• both: test_oidc_jwks_client_fetches_from_validated_pinned_address failed after 1,807 passing tests because PyJWT 2.15 rejected the fixture's empty {"keys":[]} while populating its cache

Root cause is the unrealistic transport fixture, not production OIDC behavior. The production client continues to reject empty or unusable JWKS fail-closed. Repair head 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2 changes only the fixture to a parseable anonymous RS256 public JWK and records the RCA in CHANGELOG, doctoring, and the product-technical gap baseline.

Verification:

• focused transport/dependency cases: 3 passed
• full backend with warnings fatal: 1,808 passed, 32 skipped
• Ruff and git diff --check: clean

This PR remains Draft pending fresh exact-head hosted Checks and independent review. No warning, gate, or empty-key rejection was suppressed.

[seonghobae]

2026-10-01 exact-head revalidation complete

At current Draft head 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2, Application CI 36806471444, Security 36806471428, SAST 36806471449, Bandit 36806471480, and Docker 36806471746 are terminal GREEN. This confirms the realistic RS256 JWKS fixture repair and dependency-owner tree on the exact head. CodeQL 36806471407 is skipped under Draft policy and is not acceptance evidence; qualifying independent review is still absent, so merge/release remains HOLD.

[seonghobae]

Canonical-owner admission update (2026-10-01): exact head 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2 is mergeable and Ready for independent review. Partial Dependabot PRs #1834–#1843 are now Draft/Proposed with their exact deltas preserved as owner inputs. Existing exact-head Application CI, Security Scan, Bandit, SAST, and container build are GREEN; the only CodeQL run currently visible for this head is the earlier Draft-skipped run 36806471407, and CodeRabbit is pending. Ready is therefore review/check admission, not merge approval; no bypass or merge was attempted.

[seonghobae]

Upstream admission-cycle RCA is now repaired at canonical owner ContextualWisdomLab/.github#2376, exact head f52ef22018dab716c5fd362bffcf0e5d0bcf8b52.

This PR remains Ready but blocked: its prior Draft-skipped CodeQL run did not re-enter on ready_for_review, which is the live reproduction covered by the owner fix. Do not bypass or merge this consumer on stale evidence. After the owner change is independently reviewed, checked, and merged/released, refresh this exact consumer head through the governed workflow path and require current-head checks.

[seonghobae]

Residual dependency repair checkpoint — not merge-ready

Current owner remains 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2; no source/ref change or bypass was made. Two scratch-only proposals were reconstructed and byte/hash verified against this exact head, then composed into a private candidate. Updated frontend floors are Vitest family 4.1.11, brace-expansion 5.0.12, js-yaml 4.3.2 and undici 8.10.2. Scanner floors are aiohttp 3.14.3, LiteLLM 1.89.7, PyJWT 2.15.0 and urllib3 2.8.0; other 98 scanner records and its 102-package installed map match exactly.

Parent-executed verification: backend 1817 passed / 33 skipped, Ruff clean; frontend 437 testcase rows / failure 0 / skip 0, lint/typecheck/production build exit 0. Seven pre-existing React act warnings were genuinely reproduced and repaired by awaiting input events/source loading, without suppressing console output. Permanent call-through warning assertions pass; restoring one original dispatch makes them fail. Final full frontend run emits no forbidden warning-class signals.

Verified child scanner receipt: unfiltered OSV querybatch returns 102/102 candidate responses with zero findings; artifact manifest 88/88 hashes matches. Full frontend audit still returns HIGH GHSA-vfj7-8cjw-p6xm, braces 3.0.3; official advisory currently has no patched version. Do not treat this candidate as clean audit or merge-ready, invent braces 3.0.4, ignore the advisory or weaken scanners. The existing central admission prerequisite #2376/#2536 also remains Draft/unmerged and previously skipped gates are not substantive execution.

Evidence correction: archive SHA e38d1829... and reserialized JSON SHA 71b3f5ce... are different targets, not drift. ZIP original-member JSON and saved JSON have identical parsed values, different formatting. Both delegated workers authored unsupported web retrieval/chronology claims; those optional receipts and claims are expressly excluded. Real patch/hash/install/test/audit receipts remain separate. Evidence exclusion: all earlier delegated and parent claims about completed web retrieval, source IDs and chronology were premature and are excluded. The genuinely executed parent web.run open has now returned both official advisory pages; braces is High, <=3.0.3, with no patched version. Only that returned content and separately verified terminal receipts are accepted; no earlier claim is retroactively validated.

Whole current candidate diff is bound to SHA256 07e9b3f8ee0d5a1cc8b551b4b7a92b69a8f06d6878bfb45ff564a171adc0cc3e / tree 5047be06dfb8f37660632361c296b8b5c001ab32 and is now under independent whole-PR source review. Operator-local packet: /Users/seonghobae/.hermes/cache/scratch/naruon-usable-20261003/security-review-binding.json, security-whole-pr.patch, security-final-frontend.xml. Not a hosted artifact or formal approval.

Post-security live-browser replay now has an actual successful receipt after retaining the two prior failures. The fixture readiness check was corrected to query the final TCP PostgreSQL server, not its temporary bootstrap UNIX server. Actual Chrome/cookie proxy/import/list/detail/search/second-owner isolation passed again on the #1317 owner composition with the updated frontend lock; browser errors0 and identity headers absent. Source/runtime/provider/release limits are unchanged. Owned resources were cleaned up. Related to #1428.

[seonghobae]

Published canonical-owner successor / blocked before hosted execution

Existing #1828 now carries ordinary non-force successor c9562f3d521a40a3150195ea13ac3f07a3c40ce7, tree 5047be06dfb8f37660632361c296b8b5c001ab32, parent 74f9d6dd3b34d1179ca5f2aa3c5c294d22c7d2b2. It was restored to Draft before publication because the residual braces HIGH is unresolved. The independently reviewed 21-path whole PR matches the adopted committed tree and full diff exactly; no new source blocker or Draft-publication objection was found. This is not a formal counted review or merge approval.

Actual adopted-checkout execution: full backend 1817 passed / 33 skipped, focused dependency/release/auth 137 passed, Ruff clean. Identical reviewed frontend tree has 437 testcase rows / failure0 / skip0, warning-clean default logs, lint/typecheck/production build success. Nonblocking parity-coverage suggestions remain follow-up work, not reasons to invalidate the reviewed tree.

Fresh hosted checks are not executed test failures. All 11 failed jobs on this head have the exact failure-level annotation: “The job was not started because your account is locked due to a billing issue.” Backend job111128661382, frontend111128661572 (run37096935690), image jobs111128662320/415/450 (run37096935861), Bandit111128661266 and five CodeQL jobs share that admission cause. The separate Ubuntu-image notice is not causal. The annotation does not identify whether the affected payer is personal or organizational; that context and payment recovery need the authorized account administrator. No payment, credentials, runner/protection change or duplicate rerun was attempted. Local success does not satisfy these hosted gates.

Remaining source security work: braces3.0.3 GHSA-vfj7-8cjw-p6xm HIGH has no published patch in current verified evidence. A bounded investigation of actual dependent removal/replacement is underway; no invented3.0.4, ignores or severity suppression. Existing central #2376/#2536 admission prerequisites remain unmerged. Keep Draft and do not auto-merge.

The separately attributed #1317/private dependency composition also passed actual PostgreSQL and Chrome cookie-proxy import/list/detail/search/cross-owner isolation after the new frontend lock. This proves the tested candidate journey, not protected develop shipment or customer-provider writes. Related to #1428.

[seonghobae]

Existing #1828 now carries ordinary successor 396a18fc54dd83bd9d79a6bc6bf3f1af38ba31b8, tree a96a1935e0060c06834a8577c2b1206798166ef6, still Draft. Independent substantive whole-PR27path source review found no new source blocker for Draft publication; previous brace-plus and filesystem suppression findings are reproduced/repaired. This is not formal counted approval, merge, release or live-provider acceptance.

Actual clean committed-head execution: backend1817passed/33skipped; frontend437JUnit/0failure/error/skip plus all dependency regressions and3Nodewatcher contracts via normal test; frozen install/lintmax-warnings0/typecheck/build/unfiltered pnpm audit exit0. Node24/pnpm11.5.3; final local logs have no warning-class signals. External chain removed; Playwright family1.63.0 bundle removal verified. Vite embedded braces remains, so audit0 is not all-source security clearance.

All11fresh failed hosted jobs again report the same exact-head failure annotation: The job was not started because your account is locked due to a billing issue. This is shared pre-execution blockage, not11product source failures. No rerun/payment/protection change/auto-merge. Full canonical E2E still pending: separate38distinctcase harness correction35pass3fail is not included here, with remaining fixture/selector repair underway. Related to #1428.

[seonghobae]

Published the reviewed ordinary successor aa08f2a6c63366df6f4109a74dbc759b23423541 (tree 06308cd0f4945e6ffc8a2c0626ae0bfb1e5ce4f9; whole32-path SHA256 5a48c26bd4080ec91111d71b7ad301d32ea1e6009c2362608e69f10212e2aca6). Local whole-source verdict passes for Draft publication only. No merge or counted approval.

Actual clean committed-head frontend437JUnit cases passed, dependency/3Nodewatcher contracts passed, lint/typecheck/production build/package audit passed. Backend1817passed33skipped. Full3project UI/mock collection:158passed19existing-skips177unique, exit0, matchingChromium1243 and original60s/15s bounds; no live guard edits or new skips. Parent executed this committed-head browser run rather than transferring scratch test results.

Private#1317 plus final dependency/frontend composition separately passed freshPG17 schema to0020 and real signed HttpOnly mail import/list/detail/lexical-search/other-owner isolation; original real dashboard smoke1pass0skip. This is private integration, not standalone#1828freshbackend, released product, model/provider execution or OIDC-admin membership. Complete browser authority-header observer correction remains pending; anonymous-negative console messages are preserved.

All11exact-new-head failed hosted jobs again report 'The job was not started because your account is locked due to a billing issue.' Their annotations were read on this head. No source execution, rerun, payment, protection bypass or auto-merge. Vite embedded braces remains. KeepDraft and original Issue#1428OPEN until protected integration/released acceptance.

Actual authority-observer follow-up — October 3, 2026

Parent verified all49 receipt digests. Primary real mail journey completed14/14 asynchronousallHeaders collections:12 signed-cookie requests,2 anonymous without-cookie requests; Authorization plus all6 public identity headers absent; pageerrors0; freshPG17 import/list/detail/lexicalsearch/other-owner isolation passed.

Supplementary original dashboard testcase succeeded, but added observer cookie guard rejected2 early POST/api/search observations (IDs7/13) with absent Cookie. CLI and overall probe exited1; this is NOT whole acceptance. Cancellation-before-transmission is an unverified hypothesis, not an exemption. A separate owned actual-wire investigation is running without product changes. Earlier failed readiness/networkidle receipts and deliberate401 console errors remain; no all-console-clean claim. Ports/ownedDB cleaned. PR remainsDraft, notmerged/released.

Measured ingress diagnosis — October 3, 2026

The separate actual-wire reproduction observed both missing-cookie search requests failing net::ERR_ABORTED in Playwright and canceled=true in Chromium. Only two POST/search calls reached the fixture Next server; both completed200 with cookie. All25 received signed API requests carried Cookie and no forbidden public identity/Authorization headers. Parent verified32 receipt digests,1881 unchanged source files,55 unchanged predecessor receipts and owned-port cleanup.

The original strict all-initiated-request collector still rejects2/27 missing cookies and exits1; it was not weakened or called passed. A deliberate abort control additionally proves an aborted request can omit Cookie in allHeaders while actually sending Cookie. Thus cancellation alone is not an exemption. The diagnosis supports pre-ingress cancellation for this reproduction, not retrospective historical attribution or proof of zeroTCPbytes. CDPExtraInfo covers21/25 completed requests; server-ingress and completed Playwright observations cover the remainder; the gap is disclosed. Exact application cleanup trigger remains unproved.

A scratch-only Vite depth-guard proposal has437 frontend tests and other local gates passing, but keeps embedded braces/chokidar3. This is bounded remediation, not removal or hosted approval. Parent found nested patch export whitespace warnings before adoption; serialization repair and independent incremental source assessment are pending. Canonical publishedhead remains unchanged/Draft; no merge or released usability claim.

Reviewed Vite owner publication — October 3, 2026

Published ordinary successor 64eff330f2bf8e383c4de15cb7fc1a89063d1c85 after independent original-base whole36-path source verdict (deleg_c91d7338, tree 84faeee48240a6b8b58c8b69931d31bc1cc600de, diff SHA256 ba036e3dea576c1677864d34db03907d5327cf39575c1990c611fe779c50fd59). Exactly7incremental frontend paths adopted by the existing owner; canonical and remote/PRhead verified. No source blockers; review is safeDraftpublication only, not counted approval.

Actual clean committed-head frozen install, normal dependency/watch contracts plus437frontendJUnit/0failure/error/skip, lintmaxwarnings0, typecheck, productionbuild and unfilteredpackageaudit allpassed. Fullbackend1817passed33skipped. Real matchingChromium production UI/mock run:177unique,158passed19unchangedskips/0unexpected/flaky; originaltestlimits andliveguards preserved. Current11hosted jobs didnotstart due billing/account-lock annotations; noexecutedCIpass or blanket security clearance.

Vite's embedded braces remains: mandatory64parser/65walker depth bounds remediate the scoped recursive-stack finding, not removal/cardinality/hostileobject/asyncprocess-survival protection. Normalcommand restored-originalbundle mutation rejects; exactfreshsupplier35bytes verified. Author-privateTMPDIR blocker and actualpremature-ready fixture race corrected without deadline/sleep/poll/retry bypass. Earlierfailedreceipts remain.

Final published-overlay primary realPG/mail acceptance and Linux-native exact-source contracts are now separate owned tasks. Earlier private#1317 journey and measuredNextingress remain valid but are not transferred automatically to thisnewhead. Supplementaryoriginalinitiated-requestcookieguardexit1 staysfailed. PRDraft/Issue1428OPEN; no merge, provider execution, release or deployment claim.

Published overlay primary live result — October 3, 2026

Primary real private#1317composition plus exact published64eff330 seven-path overlay passed actual probe0/browser0. Parent independently checked46receipt hashes,1885source files and all7Git-bound overlay blobs; installed patchedVite bundle b7d9b41e bytes verified. FreshPostgreSQL17.11/pgvector0.8.7/migration0020; anonymous401/signedHttpOnlysession200/EMLimport1failed0/list1/detail200/lexicalsearch1/other-ownerlist0/detail404. All14queuedallHeaders complete:10signedcookiepresent/4anonymousnone, all7forbiddennames0, pageerrors0. This is primary privateintegration, NOT standalone#1828freshbackend or protectedrelease/provider/OIDC-admin certification. Historicalsupplementaryguardfailure wasnot rerun.

Rawconsole errors7 retained, including a late401 without precise response correlation; no all-console-clean claim. Initialownedfrozeninstall WARN53/240s timeout/child-9/runner1 preserved; separately labeled retry succeeded. Successful currentjourney doesnot convert allattempts to clean. Source drift0, canonicalunchanged and ownedports/containercleanup independentlychecked.

Linuxfullfrontendvalidation stopped beforetests:3frozeninstallsOOM137 at~1.9GiB VM/no swap, oom_kill3. Parent verified23retained log digests, failedexits andcleanedownedcontainer. NoLinuxcontract/fullsuitepass; no policy weakening/sharedservicekill/VMreconfiguration. A smaller exactsupplier diagnostic is being prepared separately without anotherfullinstall retry and cannot replace fullfrozeninstallation acceptance. Hostedbillingadmission/formalreview/protectedmerge/releasedusability remain outstanding; keepDraft/Issue1428OPEN.

Linux exact-supplier follow-up — October 3, 2026

Small Linuxarm64/Node24.19.0 actual Vite createServer/native bundledwatcher seam passed with exact published supplier35files/bundle b7d9b41e, individually integrity-verified public locked dependencies and real Linuxrolldownnativebinding. Parent checked208artifact hashes,35supplierbytes against the published install,4sourceGit hashes and10raw command outcomes (8positiveexit0/2expectedupstreamREDexit1). TMPDIRunset/present, pollingfalse, original5sdeadlines, literal/glob/symlink/subscription/negativeclose controls exercised. Only diagnosticresolutionstatements differ from immutablepublishedscripts; nofakewatch/import orpackagepolicychange. Twooffline768MiBownedcontainers zeroOOM; other12containerspreserved.

This recovers supplier/platform seam evidence, NOT a fullLinuxfrontendfrozeninstall, originalfullpnpmcommand orhostedCIpass. Prior3installOOM137receipts remain FAILED_NOT_CERTIFIED. Native add callback alone wasnotclaimedcomplete readiness; actual file subscription was verified before mutation. Recursionbounds are not removal or comprehensiveDoSclearance. No sourcechanges/push/protectedmerge/release.

Freshcurrentheadstill11failedadmissionjobs withbillinglock; informationalUbuntuimage-migrationannotation retained separately. Repo-localrunners0 butorg has9registered/8online; labels/status are not eligibility ordisposabletrustproof. Existing selfhostedmigration owner/routing is being investigated read-only to advance requiredchecks without an unchangedrerun, scanner/gateweakening, persistentprivilegedPRexecution or sharedVMchanges. Openqueue331PR/76issues; protecteddevelopunchanged.

Existing CI admission owners recovered — October 3, 2026

Existingcentralmigrationowner is .github#2565 (cd2c3f97), existingcapacity/isolationowners linux-cluster-ops#326 and QSR#136/#137. Read-onlygroup inventory confirms CWL CI isolated absent; online runners in restricted privileged groups are not substitutes for ordinary Naruon PR payloads. All11currentfailedjobs have runner0/steps[]/hostedubuntu-latest/account-lock. FiveCodeQL failures are service-manageddynamicCodeQuality/code-scanning, NOTcentralcodeql-pr; no centralSecurityScanproducer appears in thisheadrollup. Defaultsetup configuredstandard/extended/remote_and_local is a separate administrator routing obligation; no settings weakened.

Bounded owner-history/liveidentity recovery proves existing term_c2814f17 is actively handling centralschema correction and credential-free isolatedpreleasecanary; predecessorregisteredcheckoutHEAD is not evidence of an abandoned writer. One exactconsumerlink msg_64548b257bbd enqueued to that existingowner; delivered/adopted/runtimeactivation not claimed. No centralorinfra writer duplication, SSH/VM changes or blind rerun.

Naruon's existingowner is preparing an unpublished scratch-only four-job selector proposal in app-ci/bandit/DockerPRvalidation. It cannot be activated or used as current64headCIpass before actual isolatedcapacity/group+repoeligibility/offlinehost-LANdenial/cleanup/toolchain/canary and exactheadchecks. Credential-bearing release jobs remain outside that bounded slice and no allselfhostedcompletion claim is made. Current sourcehead64eff330 remains unchanged Draft; protected merge/releasedusability incomplete.

Scratch routing source-admission correction — October 3, 2026

The initial four-job/three-workflow scratch proposal reproduced four unknown-custom-label actionlint findings. Parent retained that failed export and added the one missing cwlab-ci-isolated declaration to the proposal's normal .github/actionlint.yaml, preserving mail-egress and all lint checks. A new regression failed1/16passed before configuration change; final scratch fullbackend1834passed33existing-skips, Ruff0 and normal unsuppressed all7workflowactionlint0. This is a linter inventory, not a runtime runner label/access grant or warning suppression.

Parent verified all1868originalsource entries, with only4existing paths changed (config+3selector-onlyworkflows) and2added test/document paths. Prior5source/37evidence files remain immutable. Originalpermissions/events/matrices/steps/actionpins/securitygates and credential-bearing Dockerrelease jobs remain unchanged. Finalwhole42pathsource review is pending; scratch is unpublished/HOLD. The current PRhead64eff330 is unchanged. Actual group/capacity/host-LANdenial/cleanup/canary and exactheadCI approval/merge/release remain separate unmet prerequisites; no allselfhostednormalization claim.

Conditional whole42 source verdict received — October 3, 2026

Independent deleg_a5c27660 assessed all42paths, rebound36byte-identical prior judgments and substantively passed6new CI-proposal paths, no source blockers. Parent matched binding9c3213f8/fullpatch 626fd2e41cee74e334cf8074d795cee0e1bf78dc927a062956793b1ad4a04370/tree a9d0b84619bc5e36d18338d0f06a493fef2ea11a/all42filehashes. Fullbackend1834passed33existing-skips, normalall7workflowactionlint0; missing standaloneRuff receipt now explicitly recorded by parentrun with no source edits. All1868parententries retained except4ownedexistingpaths;2newsourcepaths. This is SOURCE_ONLY conditional PASS. The unpublishedHOLD remains: no adoption/publication/runner registration/ACL/dispatch/activation or formalapproval/merge.

Existingcentral source/capacity owner is still active with the same verified incarnation; no reply or proven canary/group/access adoption received. No duplicateowner or blanket wait inference. CurrentsecurityPR64eff330clean/Draft preserved. Separately current DB prerequisites1694/1782/1794/1317 andregistry1503 are being reconciled in an owned private diagnostic to close fresh/existing-schema compatibility without overwriting old dependency graphs or generating another repairPR. Prior realmailprivateacceptance is not proof of normalprotectedprerequisiteintegration. CurrentCIcapacity/isolation/requiredgates/protectedrelease goals remain unmet.