Skip to content

Commit 678d6d6

Browse files
committed
chore(changeset): declare the three new metadata-core exports as Clause-② yes (widening)
The contract review read appOf, pairOf and isPairOf as a widening of the published @objectstack/metadata-core entry; level stays patch and Metadata-protocol stays none. The unit table's docblock now says its rows' type, scope and namespace are the App resolver's future inputs. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L9qibw7rMHd8P2YJ7SyYZi
1 parent 979d839 commit 678d6d6

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

‎.changeset/29594-customization-pair-lookup.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
refactor(metadata-core): the customization pair of a package is looked up through the App that carries it
1010

11-
Clause-②: no
11+
Clause-②: yes (widening)
1212
Metadata-protocol: none
1313

1414
`@objectstack/metadata-core` exports `pairOf(base)`, `isPairOf(pairId, base)` and `appOf(packageId)`: the pair of a package is `customizationPackageId(appOf(base))` (ADR-0146 D3, with the customization unit being the App per ruling record 6691022506). `appOf` is the identity today, so every package is still its own App for customization and every answer is the one `customizationPackageId` / `isCustomizationPairOf` gave before: the same pair ids, the same refusals, the same served overrides, write gates, list and layered reads, uninstall refusal, flow precedence remedy and datasource import landing.

‎packages/metadata-core/src/customization-pair-lookup.test.ts‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ import { appOf, isPairOf, pairOf } from './customization-pair-lookup.js';
1010
* package, a `sys` kernel package, a manifest with no namespace — because
1111
* `appOf` is the identity until the ensure door resolves a member to its App.
1212
* Each row pins the literal pair, so a resolver that moves one package to
13-
* another App reds that row by name.
13+
* another App reds that row by name. The rows' `type`, `scope` and `namespace`
14+
* are read by nothing today: they are the App resolver's inputs when it lands.
1415
*/
1516
const ROWS: ReadonlyArray<{ shape: string; manifest: { id: string; type?: string; scope?: string; namespace?: string }; pair: string }> = [
1617
{

0 commit comments

Comments
 (0)