Skip to content

feat: support read-only external references across ct projects - #162

Open
bwl21 wants to merge 4 commits into
eqrm:mainfrom
bwl21:codex/issue-143-external-references
Open

feat: support read-only external references across ct projects#162
bwl21 wants to merge 4 commits into
eqrm:mainfrom
bwl21:codex/issue-143-external-references

Conversation

@bwl21

@bwl21 bwl21 commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

Closes #143

Summary

  • add state v2 external bindings with in-memory v1 migration and globally unique logical keys
  • add generic registry-backed ct use, ct unuse, state listing/removal/rekeying, and live hard-identity validation
  • resolve external resources read-only across hierarchy, dynamic rulesets, permissions, and other logical reference positions without admitting them to apply or destroy inputs
  • add structured blocking diagnostics and ct ownership check for explicit cross-project coordination scopes
  • document the ownership model, CLI workflow, identity contract, and all supported resource types

Verification

  • npm test -- --reporter=dot — 1141 passed, 5 skipped
  • npm run typecheck
  • npm run lint
  • npm run format:check
  • npm run build
  • node .github/scripts/docs-staleness.mjs

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.

feat: support read-only external references across ct projects

1 participant