feat: consume the framework from GitHub Packages — retire .framework-sha

[coccyx]

One-sentence summary: every framework dependency now comes from GitHub Packages (@criblio scope, published by framework PR #30) — the file:../ links, the .framework-sha pin, and the framework-clone CI machinery are gone.

What changed

• Imports: @cribl/app-utils → @criblio/app-utils, @cribl/app-tooling → @criblio/app-tooling (54 files, mechanical sed).
• package.json: registry versions (^0.5.0 app-utils, ^0.2.0 app-tooling, ^0.1.0 agent-protocol / cell-harness / cell-workspace).
• .npmrc routes the @criblio scope. No auth line committed — locally that lives in ~/.npmrc (see the rewritten CLAUDE.md section), and in CI the release-build action writes it from registry-token.
• ci.yml / release.yml: release-build action in registry mode (@7ef8eb4), .framework-sha deleted.
• New update-lockfile workflow: regenerates package-lock.json on a branch in CI for machines without a registry token (used to bootstrap this very branch — the lockfile's @criblio entries resolve from npm.pkg.github.com with integrity hashes).
• CLAUDE.md: SHA-pin section replaced with GitHub Packages guidance (one-time ~/.npmrc token, bump flow, framework-dev flow).

Validation

This PR's build check is the end-to-end proof: registry-mode npm ci with GITHUB_TOKEN, full verify (lint/test/tsc), packaging, and — with the validation-workspace secrets — a live deploy + Playwright smoke of the exact candidate. Local full suite also run against the same package sources via the framework checkout.

One-time local setup (everyone)

gh auth refresh -h github.com -s read:packages, then put //npm.pkg.github.com/:_authToken=<gh auth token> in ~/.npmrc (or use a classic PAT with read:packages).

🤖 Generated with Claude Code

https://claude.ai/code/session_0158jez4WfWj6ttmaxh3HEbT

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​criblio/​agent-protocol@​0.1.1	N/A	N/A	N/A	N/A	N/A
	@​criblio/​app-tooling@​0.2.0	N/A	N/A	N/A	N/A	N/A
	@​criblio/​app-utils@​0.5.1	N/A	N/A	N/A	N/A	N/A
	@​criblio/​cell-harness@​0.1.1	N/A	N/A	N/A	N/A	N/A
	@​criblio/​cell-workspace@​0.1.1	N/A	N/A	N/A	N/A	N/A

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @protobufjs/float is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@criblio/cell-harness@0.1.1 → npm/@protobufjs/float@1.0.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@protobufjs/float@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report