Split out of PR #6.
What was removed and why
38cec72 added src/scope-projector.js plus this dependency:
"@chittyos/schema": "file:../../CHITTYFOUNDATION/chittyschema"
That path escapes the repository into a sibling checkout on one VM. It resolves there as a symlink, so local npm ci, npm run build, and wrangler deploy --dry-run all pass — which is exactly why it went unnoticed. It cannot resolve anywhere else:
@chittyos/schema is not published (npm view @chittyos/schema → 404)
- Cloudflare Pages clones only this repo
The Pages build failed with:
✘ [ERROR] Could not resolve "@chittyos/schema/scope-projector"
src/scope-projector.js:10:37
Pages succeeds on main and failed on the branch, so merging would have broken main. The branch had never been pushed, so this was the first CI run that ever saw 38cec72.
src/scope-projector.js
- the import at
src/index.js:5
- both
traceScopeLog call sites (src/index.js:130, :328)
- the
file: dependency
Nothing was lost from production — the code could never build, so it never deployed. It remains in history at 38cec72.
To re-land
The capability itself is wanted: projecting forensic investigation lifecycle events into the canonical scopes table as trace_investigation. It needs @chittyos/schema consumable from CI first. chittyschema-overlord owns that decision — likely publishing to a registry (npm or GitHub Packages) and adding auth to the Pages build environment. Vendoring the module into this repo was considered and rejected: forking a canonical schema artifact into a leaf app is drift by construction.
@chittyos/schema@0.2.0 already declares the subpath export, so the import is correct; only distribution is missing:
"./scope-projector": {
"import": "./connectivity/dist/scope-projector.js",
"types": "./connectivity/dist/scope-projector.d.ts"
}
Worth checking fleet-wide
Any other repo depending on @chittyos/schema via a file: path has the same latent break — green locally, unbuildable in CI.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PSJp8eaY4ABrZKGkcD1xgM
Split out of PR #6.
What was removed and why
38cec72addedsrc/scope-projector.jsplus this dependency:That path escapes the repository into a sibling checkout on one VM. It resolves there as a symlink, so local
npm ci,npm run build, andwrangler deploy --dry-runall pass — which is exactly why it went unnoticed. It cannot resolve anywhere else:@chittyos/schemais not published (npm view @chittyos/schema→ 404)The Pages build failed with:
Pages succeeds on
mainand failed on the branch, so merging would have brokenmain. The branch had never been pushed, so this was the first CI run that ever saw38cec72.Removed in d457a74
src/scope-projector.jssrc/index.js:5traceScopeLogcall sites (src/index.js:130,:328)file:dependencyNothing was lost from production — the code could never build, so it never deployed. It remains in history at
38cec72.To re-land
The capability itself is wanted: projecting forensic investigation lifecycle events into the canonical scopes table as
trace_investigation. It needs@chittyos/schemaconsumable from CI first. chittyschema-overlord owns that decision — likely publishing to a registry (npm or GitHub Packages) and adding auth to the Pages build environment. Vendoring the module into this repo was considered and rejected: forking a canonical schema artifact into a leaf app is drift by construction.@chittyos/schema@0.2.0already declares the subpath export, so the import is correct; only distribution is missing:Worth checking fleet-wide
Any other repo depending on
@chittyos/schemavia afile:path has the same latent break — green locally, unbuildable in CI.🤖 Generated with Claude Code
https://claude.ai/code/session_01PSJp8eaY4ABrZKGkcD1xgM