@reqvire-org/ads 0.3.21 → 0.3.23

package/dist/skills/ads-break-ui/references/contracts.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/dist/skills/ads-designer/references/contracts.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/dist/skills/ads-import/references/contracts.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/dist/skills/ads-migrate/references/contracts.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/dist/skills/ads-motion/references/contracts.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/dist/units.mjs

@@ -2,7 +2,7 @@ import { existsSync, readFileSync, readdirSync } from "node:fs";
 import path from "node:path";
 import ts from "typescript";
 import postcss from "postcss";
-import { adsFileRole, isDevelopmentFile, isInside } from "./config.mjs";
+import { adsFileRole, isDevelopmentFile, isInside, scenarioIdentity } from "./config.mjs";
 import { importResolver } from "./boundaries.mjs";
 import { documentationFilePolicy, isProjectDocument, projectDocumentFiles } from "./project-documents.mjs";
 import { foundationFiles, foundationImportTarget } from "./token-policy.mjs";
@@ -98,8 +98,33 @@ export function inspectUnits(options) {
   // Runtime entry conventions keep directory ownership stable when an optional
   // preview is removed. A flat scenario family still denotes separate owners.
   const sameName = name => name.replace(/[-_]/g, "").toLowerCase();
-  const flatFamilies = new Set(files.filter(file => !adsFileRole(file) && /\.scenario\.[cm]?[jt]sx?$/.test(file)).map(file => path.posix.dirname(file)));
+  const legacyFlatFamilies = new Set(files.filter(file => !adsFileRole(file) && /\.scenario\.[cm]?[jt]sx?$/.test(file)).map(file => path.posix.dirname(file)));
+  const canonicalDefaults = new Set();
   const directories = new Set(files.filter(file => /(?:^|\/)Scenario\.[cm]?[jt]sx?$/.test(file)).map(file => slash(path.dirname(file))));
+  // A canonical marked default is the development entry of the same directory
+  // owner as Scenario.tsx. It needs no production module or empty contract to
+  // retain that boundary. Preserve explicit flat IDs and existing peer families.
+  for (const file of files.filter(file => adsFileRole(file) === "scenario")) {
+    const directory = path.posix.dirname(file);
+    if (legacyFlatFamilies.has(directory) || scenarioIdentity(path.join(dsRoot,file),dsRoot) !== directory) continue;
+    const ast = ts.createSourceFile(file,readFileSync(path.join(dsRoot,file),"utf8"),ts.ScriptTarget.Latest,true);
+    const declaration = ast.statements.filter(ts.isVariableStatement).flatMap(statement=>statement.declarationList.declarations)
+      .find(declaration=>ts.isIdentifier(declaration.name)&&declaration.name.text==="scenario");
+    let metadata = declaration?.initializer;
+    while (metadata && (ts.isAsExpression(metadata)||ts.isSatisfiesExpression(metadata)||ts.isParenthesizedExpression(metadata))) metadata=metadata.expression;
+    if (!metadata || !ts.isObjectLiteralExpression(metadata)) continue;
+    const id = metadata.properties.find(property=>property.name && (ts.isIdentifier(property.name)||ts.isStringLiteralLike(property.name)) && property.name.text==="id");
+    if (id && (!ts.isPropertyAssignment(id)||!ts.isStringLiteralLike(id.initializer)||id.initializer.text!==directory)) continue;
+    // An unresolved spread/computed key may supply or overwrite an explicit ID.
+    if (metadata.properties.some((property,index)=>ts.isSpreadAssignment(property) && (!id || index>metadata.properties.indexOf(id))
+      || property.name && ts.isComputedPropertyName(property.name))) continue;
+    directories.add(directory);
+    canonicalDefaults.add(directory);
+  }
+  // Marked flat siblings still outrank a directory index/runtime barrel. Losing
+  // the final legacy spelling must not merge otherwise unrelated peer owners.
+  const flatFamilies = new Set(files.filter(file => /\.scenario\.[cm]?[jt]sx?$/.test(file)
+    && (!adsFileRole(file) || !canonicalDefaults.has(path.posix.dirname(file)))).map(file => path.posix.dirname(file)));
   for (const file of files.filter(file => /^(?:components|patterns)\/.+\/tokens\.json$/.test(file))) directories.add(path.posix.dirname(file));
   for (const file of files.filter(file => /\.ads\.contract\.[cm]?ts$/.test(file))) {
     const directory=path.posix.dirname(file);

package/docs/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Unreleased
 
+## 0.3.23
+
+- Preserve directory ownership when its last legacy composition/scenario entries
+  migrate to canonical `.ads.` roles. Require no artificial runtime entry or
+  empty contract; retain explicit flat IDs and existing flat peer families.
+- Keep fully migrated flat scenario siblings separate beside directory export
+  barrels. Version 0.3.22 was tagged; publication was cancelled before these
+  additional full-migration checks completed.
+
 ## 0.3.21
 
 - Add statically read TypeScript owner contracts and canonical `.ads.` development

package/docs/CONTRACTS.md

@@ -238,7 +238,10 @@ MCP before replacing a package used by a running server. Then:
 5. Dry-run/apply with `ads_apply_patch`, or a genuinely coupled transaction.
 
 Migration never edits live source or bypasses gates. It retains stable scenario
-IDs and check case IDs. An optional static `scenario.id` preserves a legacy
+IDs, check case IDs and directory ownership. A canonical `<Owner>.ads.scenario.tsx` is the same
+development entry as `Scenario.tsx`, even without a production entry or owner
+contract. Explicit flat IDs and existing flat peer families remain separate.
+An optional static `scenario.id` preserves a legacy
 identity when a renamed filename would otherwise be ambiguous; it must stay
 inside the owning unit and be unique. Whole-file or unimportable private behavior subjects stay
 in legacy registration with a note until deliberately resolved. Unknown runner

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reqvire-org/ads",
-  "version": "0.3.21",
+  "version": "0.3.23",
   "type": "module",
   "description": "A design system your agent can see and shape. Your components. Your look. Your code.",
   "repository": {