Skip to content

Refresh public claim boundary reports#161

Merged
svy04 merged 1 commit into
mainfrom
codex/public-claim-boundary-freshness
Jun 20, 2026
Merged

Refresh public claim boundary reports#161
svy04 merged 1 commit into
mainfrom
codex/public-claim-boundary-freshness

Conversation

@svy04

@svy04 svy04 commented Jun 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • Refresh generated dead-export candidate reports from the current Knip ordering.
  • Refresh public-claim-boundary report hashes so verify:privacy is current on origin/main.
  • Preserve the public claim boundary: Metaforge remains Meta + MFH + Orchestra OS, with OpenClaude as runtime substrate.

Verification

  • bun install --frozen-lockfile
  • bun run build
  • bun run typecheck --pretty false
  • bun test scripts/product-dead-export-candidates.test.ts scripts/product-static-analysis-remediation-queue.test.ts src/bridge/sessionRunner.test.ts
  • bun run product:public-claim-boundary
  • bun run verify:privacy
  • bun run product:quality (exit 0; keeps the local VS Code CLI unavailable boundary explicit rather than upgrading readiness claims)
  • git diff --check

Claim Boundary

  • No source code or public marketing copy changed.
  • No new provider/live model/external calls or protected actions were added.
  • Public comparison, superiority, production-readiness, and external-validation claims remain blocked.

@svy04 svy04 merged commit b602d2c into main Jun 20, 2026
6 checks passed
@svy04 svy04 deleted the codex/public-claim-boundary-freshness branch June 20, 2026 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant