Skip to content

[TS PBT] Pin capability-first real property candidate - #408

Closed
CaelmBleidd wants to merge 5 commits into
caelmbleidd/pbt-356-core-corpusfrom
caelmbleidd/pbt-356-core-capability
Closed

CaelmBleidd wants to merge 5 commits into
caelmbleidd/pbt-356-core-corpusfrom
caelmbleidd/pbt-356-core-capability

Conversation

@CaelmBleidd

@CaelmBleidd CaelmBleidd commented Sep 30, 2026 •

Copy link
Copy Markdown
Member

Pin the capability-first real property candidate and its bounded adapter in the PBT development corpus. Based on the core corpus PR #406; retains the upstream assertion separately from the bounded supported form and records explicit capability/protocol boundaries.

Rebased only this PR's own change onto the updated #406. All locked package tarballs now use public npm URLs; versions and integrity hashes are unchanged.

Validation: clean npm ci from registry.npmjs.org with an isolated public cache, then the upstream and bounded Vitest suites in a single worker: 4 tests passed. This validates the pinned corpus witnesses and adapter locally; it does not establish experiment advantage or production coverage. Fresh CI remains the broader gate.

@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pbt-356-core-corpus branch from ae72976 to e4f045c Compare October 12, 2026 20:55
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pbt-356-core-capability branch 2 times, most recently from 81cd92e to 921c515 Compare October 13, 2026 21:09
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pbt-356-core-corpus branch from e4f045c to b44f59b Compare October 13, 2026 21:09
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pbt-356-core-capability branch from 921c515 to 3a23fd2 Compare October 13, 2026 21:17
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pbt-356-core-corpus branch from b44f59b to 1466433 Compare October 13, 2026 21:17
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