@usableapp/cardds 0.7.95 → 0.7.96

package/dist/index.d.ts

@@ -21,6 +21,8 @@ export * from './scaffold/Centre.js';
 export * from './scaffold/slideScreen.js';
 export * from './scaffold/LayerHistory.js';
 export * from './cards/Card.js';
+export * from './cards/cardGrounds.js';
+export * from './cards/inkGrounds.js';
 export * from './cards/CardHead.js';
 export * from './cards/CardFoot.js';
 export * from './cards/CardParts.js';

package/dist/index.js

@@ -25,6 +25,8 @@ export * from './scaffold/Centre.js';
 export * from './scaffold/slideScreen.js';
 export * from './scaffold/LayerHistory.js';
 export * from './cards/Card.js';
+export * from './cards/cardGrounds.js';
+export * from './cards/inkGrounds.js';
 export * from './cards/CardHead.js';
 export * from './cards/CardFoot.js';
 export * from './cards/CardParts.js';

package/lib/guide.mjs

@@ -7,7 +7,7 @@ ORDER: find → scaffold or get → write → check. First question: has cardds
 TOOLS: find_components · scaffold_screen · get_component · list_components · check_source. No MCP: npx cardds find|scaffold|get|list|check (all take --json).
 What no checker sees:
 1. cardds is a framework you take from outside. Never edit, commit to or release cardds from a consumer project, never node_modules. What cannot be set from outside is a framework gap: STOP and tell the user exactly what you needed.
-2. Adjust from outside only, widest first: theme.css bases → knobs (--<component>-<what>) → props/slots. The theme's values are the user's call; never pick them.
+2. Adjust from outside only, widest first: theme.css bases → knobs (--<component>-<what>) → props/slots. The theme's values are the user's call; never pick them. cardGrounds() names a card the member cannot see on that theme; inkGrounds() a word or glyph they cannot read (README "Ink follows its ground").
 3. Every component is controlled like an input (state/open/value + its on…, or default…) and none knows another: the app owns the state and wires them.
 4. Import components, never copy their markup or classes: a component is the look AND the behaviour.
 5. Mobile only, big targets; never adapt it to desktop.

package/lint/rules.mjs

@@ -251,8 +251,12 @@ export function checkSource(source, file, { classes = carddsClasses() } = {}) {
     const el = elementAt(text, m.index);
     const btns = [...el.slice(tag.length).matchAll(/<Btn\b(?![\w.])/g)].map((b) => m.index + tag.length + b.index);
     if (btns.length < 2) continue;
+    // the two branches of a conditional (`last ? <Btn primary>Send</Btn> : <Btn primary>Next</Btn>`) are ONE slot: both are the forward one
+    const slot = []; let n = 0;
+    btns.forEach((at, i) => { if (i && /^\s*\)?\s*:\s*\(?\s*$/.test(text.slice(btns[i - 1] + elementAt(text, btns[i - 1]).length, at))) slot.push(n); else slot.push(++n); });
+    if (n < 2) continue;
     btns.forEach((at, i) => {
-      const forward = i === btns.length - 1, primary = /\sprimary\b(?!\s*=\s*\{\s*false)/.test(tagAt(text, at));
+      const forward = slot[i] === n, primary = /\sprimary\b(?!\s*=\s*\{\s*false)/.test(tagAt(text, at));
       if (primary !== forward) add('pager-forward-primary', 'error', at, forward
         ? 'the forward <Btn> of a worded pager is not `primary`: back and next carry the same signal. The last Btn (the step it leads to) is <Btn primary>; the back one stays plain.'
         : 'a back <Btn> of a worded pager is `primary`: only the forward one (the last) is. Drop `primary` here.');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usableapp/cardds",
-  "version": "0.7.95",
+  "version": "0.7.96",
   "license": "UNLICENSED",
   "type": "module",
   "description": "card-first mobile design system, React-first: the components in src/ are thin wrappers over the CSS contract (css/*.css stays the only truth); gallery/ shows every story live (npm run dev), tests/ measures the geometry.",