create-flowdular 0.6.3 → 0.6.5

package/agent-template/.agents/skills/auto-review/SKILL.md

@@ -69,7 +69,10 @@ implementation turn after a passing review. Use the provided
 reference code and recorded gate output. The orchestrator runs schema, dependency,
 typecheck, tests and format gates; never claim you ran a command it ran later.
 Report verification still pending when needed. Deterministic checks are independent
-of your assessment and must all pass before eject.
+of your assessment and must all pass before eject. Nobody in the sandbox can render
+the screen: the operator inspects it in the preview. For the UI check, cite the
+component code, its states and the tests as evidence; a missing rendered inspection
+is not a finding.
 
 Return exactly one fenced `auto-review` JSON object in the closing response,
 followed by the normal handoff line. Each check is a string of 20 to 4000 characters
@@ -85,7 +88,7 @@ under 32000 characters. The structure is:
     "compatibility": "Public consumers and migration or manifest evidence.",
     "lifecycle": "Resource ownership and failure-path evidence.",
     "tests": "Test paths, assertions, actual gate results or pending checks.",
-    "ui": "Rendered inspection evidence or a specific reason not applicable."
+    "ui": "Component code, states and tests, or a specific reason not applicable."
   },
   "findings": ["Severity; file:line; input/state; wrong outcome; required fix."]
 }

package/agent-template/.agents/skills/module-new/SKILL.md

@@ -72,7 +72,7 @@ migrations, releases it, then acquires the runtime lease requiring
 stays async and database-agnostic, and persistence stays on
 `@flowdular/sdk/database`.
 
-The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended, and those files win over the scaffold's; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
+The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended: the specification stays, and each translation bundle keeps its keys and gains the skeleton's, the author's wording winning on a shared key; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
 
 What is still yours after the scaffold: the real fields of the entity beyond `name`, validation bounds and stable error codes, uniqueness rules and their indexes, further endpoints and entities, screen columns and the drawer form, tests beyond identity and isolation. A business agent is a separate phase using `business-agent-design`; the scaffold does not invent one.
 

package/agent-template/.ai/agents/sandbox/frontend-engineer.md

@@ -4,6 +4,7 @@ name: 'Frontend engineer'
 purpose: 'Implement the client: contribution, views, forms, state, and API calls.'
 allowedPaths:
   - 'src/client/**'
+  - 'translations/**'
   - 'tests/**'
   - 'package.json'
 gates:
@@ -15,6 +16,7 @@ gates:
 handoff:
   - backend-engineer
   - ux-designer
+  - business-manager
 ---
 
 You own src/client: contributions, screens, forms, state and API calls. Use only the Task skill selected under Session and consult reference/design-system.md for visual changes. Extend the scaffold and copy reference/example-module/src/client where needed.
@@ -23,6 +25,6 @@ Keep fetch calls in api.ts, pass the contribution's CSRF token into mutations, u
 
 Use the canonical createClientContribution entry. Navigation must point at an existing view; widgets use registered shell slots. Missing scopes hide actions, but server authorization remains authoritative. Keep server dependencies out of client imports.
 
-Records own the page, with create/edit in a Drawer. Reuse TableCard and Table, including widths, loading and empty states. Use translated copy, all five states, and no hardcoded design values. Inspect the rendered screen before handoff.
+Records own the page, with create/edit in a Drawer. Reuse TableCard and Table, including widths, loading and empty states. Use translated copy, all five states, and no hardcoded design values. Add every key your screens read to each locale's translations/<locale>.json, without the module prefix (t('<module>.page.title') reads page.title) and with that locale's plural forms; the business manager may reword domain terms. Inspect the rendered screen before handoff.
 
 For TSRX, loop keys can read only the loop item: precompute a key on each item if it needs props or local state. Test pure mapping/filtering logic in .ts helpers. Ask the backend engineer for an endpoint or field the spec defines but the server lacks, or UX for an unresolved screen decision. Never invent a business decision the approved spec does not make (a field, state, permission or behaviour): ask for it with a questions block (Session).

package/agent-template/.ai/agents/sandbox/ux-designer.md

@@ -4,6 +4,7 @@ name: 'UX designer'
 purpose: 'Design the screens, their states, and their copy on the shared design system.'
 allowedPaths:
   - 'src/client/**'
+  - 'design/**'
 gates:
   - typecheck
   - format
@@ -12,7 +13,7 @@ handoff:
   - business-manager
 ---
 
-You own screen structure, states and copy in src/client. Use only the Task skill selected under Session, reference/design-system.md and the relevant shared component source. reference/example-module/src/client/CatalogView.tsrx is the screen example.
+You own screen structure, states and copy in src/client, and screen designs in design/. Use only the Task skill selected under Session, reference/design-system.md and the relevant shared component source. reference/example-module/src/client/CatalogView.tsrx is the screen example.
 
 Reshape the existing scaffold into a typechecking view and Drawer form. Leave fetch, api.ts and data wiring to the frontend engineer. Use readonly typed props and real domain types, not fabricated records presented as working behavior.
 

package/agent-template/.ai/policies/path-ownership.yaml

@@ -38,7 +38,7 @@ owners:
 # .ai/agents/sandbox/*.md says who writes what. Advisory at run time.
 moduleRoles:
   modules/{module}/spec/**: [business-manager, agentic-engineer]
-  modules/{module}/translations/**: [business-manager]
+  modules/{module}/translations/**: [business-manager, frontend-engineer]
   modules/{module}/src/acl/**: [backend-engineer]
   modules/{module}/src/api/**: [backend-engineer]
   modules/{module}/src/server/**: [backend-engineer]
@@ -48,6 +48,7 @@ moduleRoles:
   modules/{module}/src/index.ts: [backend-engineer]
   modules/{module}/migrations/**: [backend-engineer]
   modules/{module}/src/client/**: [ux-designer, frontend-engineer]
+  modules/{module}/design/**: [ux-designer]
   modules/{module}/src/agent/**: [agentic-engineer]
   modules/{module}/tests/**:
     [backend-engineer, frontend-engineer, agentic-engineer]

package/agent-template/.ai/policies/task-budgets.yaml

@@ -33,7 +33,7 @@ sandbox:
     messageLength: 1 to 20000 characters (packages/sandbox/src/server/turns.ts)
     briefLength: at least 8 characters (planning.ts assertBrief)
     gateTimeout: 5 minutes per gate, output capped at 12000 characters (gates.ts)
-    gateFailure: a role whose write paths cover the failing file repairs, a repair that changed nothing is not repeated by the same role, and a gate that failed runs after every turn until it passes; at most maxRepairLoops consecutive repair turns per chain, then the chain returns to the operator
+    gateFailure: a role whose write paths cover the failing file repairs, a repair that changed nothing is not repeated by the same role, and a gate that failed runs after every turn until it passes; at most maxRepairLoops consecutive repair turns per chain, then the chain returns to the operator; a review turn neither counts toward nor resets that count
     byokReads: 400 listed files, 128 KB per read (packages/coding-agent/src/drivers/byok.ts)
   review:
     chainedTurns: stop and read the transcript after four automatic handoffs on one brief

package/agent-template/.ai/skills/auto-review/SKILL.md

@@ -78,7 +78,10 @@ implementation turn after a passing review. Use the provided
 reference code and recorded gate output. The orchestrator runs schema, dependency,
 typecheck, tests and format gates; never claim you ran a command it ran later.
 Report verification still pending when needed. Deterministic checks are independent
-of your assessment and must all pass before eject.
+of your assessment and must all pass before eject. Nobody in the sandbox can render
+the screen: the operator inspects it in the preview. For the UI check, cite the
+component code, its states and the tests as evidence; a missing rendered inspection
+is not a finding.
 
 Return exactly one fenced `auto-review` JSON object in the closing response,
 followed by the normal handoff line. Each check is a string of 20 to 4000 characters
@@ -94,7 +97,7 @@ under 32000 characters. The structure is:
     "compatibility": "Public consumers and migration or manifest evidence.",
     "lifecycle": "Resource ownership and failure-path evidence.",
     "tests": "Test paths, assertions, actual gate results or pending checks.",
-    "ui": "Rendered inspection evidence or a specific reason not applicable."
+    "ui": "Component code, states and tests, or a specific reason not applicable."
   },
   "findings": ["Severity; file:line; input/state; wrong outcome; required fix."]
 }

package/agent-template/.ai/skills/module-new/SKILL.md

@@ -78,7 +78,7 @@ migrations, releases it, then acquires the runtime lease requiring
 stays async and database-agnostic, and persistence stays on
 `@flowdular/sdk/database`.
 
-The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended, and those files win over the scaffold's; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
+The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended: the specification stays, and each translation bundle keeps its keys and gains the skeleton's, the author's wording winning on a shared key; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
 
 What is still yours after the scaffold: the real fields of the entity beyond `name`, validation bounds and stable error codes, uniqueness rules and their indexes, further endpoints and entities, screen columns and the drawer form, tests beyond identity and isolation. A business agent is a separate phase using `business-agent-design`; the scaffold does not invent one.
 

package/agent-template/.claude/skills/auto-review/SKILL.md

@@ -69,7 +69,10 @@ implementation turn after a passing review. Use the provided
 reference code and recorded gate output. The orchestrator runs schema, dependency,
 typecheck, tests and format gates; never claim you ran a command it ran later.
 Report verification still pending when needed. Deterministic checks are independent
-of your assessment and must all pass before eject.
+of your assessment and must all pass before eject. Nobody in the sandbox can render
+the screen: the operator inspects it in the preview. For the UI check, cite the
+component code, its states and the tests as evidence; a missing rendered inspection
+is not a finding.
 
 Return exactly one fenced `auto-review` JSON object in the closing response,
 followed by the normal handoff line. Each check is a string of 20 to 4000 characters
@@ -85,7 +88,7 @@ under 32000 characters. The structure is:
     "compatibility": "Public consumers and migration or manifest evidence.",
     "lifecycle": "Resource ownership and failure-path evidence.",
     "tests": "Test paths, assertions, actual gate results or pending checks.",
-    "ui": "Rendered inspection evidence or a specific reason not applicable."
+    "ui": "Component code, states and tests, or a specific reason not applicable."
   },
   "findings": ["Severity; file:line; input/state; wrong outcome; required fix."]
 }

package/agent-template/.claude/skills/module-new/SKILL.md

@@ -72,7 +72,7 @@ migrations, releases it, then acquires the runtime lease requiring
 stays async and database-agnostic, and persistence stays on
 `@flowdular/sdk/database`.
 
-The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended, and those files win over the scaffold's; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
+The first entity is the middle segment of the first permission id (`inventory.locations.read` gives `locations`, table `inventory_locations`, type `InventoryLocation`); it gets the list endpoint (`.read`), the create endpoint (`.manage`), the table, the view and the tests. Every other permission becomes a constant in `X_PERMISSIONS` only; its entity is `module-update` work. A directory that already holds `spec/module.yaml` and `translations/**` (the business manager's files) is extended: the specification stays, and each translation bundle keeps its keys and gains the skeleton's, the author's wording winning on a shared key; a directory with sources is refused. In the sandbox the orchestrator runs the scaffold once the spec is approved.
 
 What is still yours after the scaffold: the real fields of the entity beyond `name`, validation bounds and stable error codes, uniqueness rules and their indexes, further endpoints and entities, screen columns and the drawer form, tests beyond identity and isolation. A business agent is a separate phase using `business-agent-design`; the scaffold does not invent one.
 

package/agent-template/docs/modules.md

@@ -124,8 +124,9 @@ skills.
 
 Files are written through the workspace Prettier, so the format gate passes
 without a rewrite. A directory that already holds `spec/module.yaml` or
-`translations/**` is extended, not rejected, and a failed run leaves nothing
-behind.
+`translations/**` is extended, not rejected: a translation bundle keeps its
+keys and gains the skeleton's, the author's wording winning on a shared key. A
+failed run leaves nothing behind.
 
 ### 3. Implement
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "create-flowdular",
-	"version": "0.6.3",
+	"version": "0.6.5",
 	"type": "module",
 	"description": "Scaffold a Flowdular application: the platform, one example module and the secrets a fresh install needs.",
 	"license": "MIT",

package/template/default/modules/example/package.json

@@ -16,7 +16,7 @@
 	"dependencies": {
 		"octane": "0.9.1",
 		"segment-state": "0.4.0",
-		"@flowdular/sdk": "0.6.3"
+		"@flowdular/sdk": "0.6.5"
 	},
 	"devDependencies": {
 		"@tsrx/typescript-plugin": "0.3.120",

package/template/default/package.json

@@ -22,10 +22,10 @@
 		"build": "flowdular module sync --apply && pnpm --filter @app/platform build"
 	},
 	"devDependencies": {
-		"@flowdular/sandbox": "0.6.3",
+		"@flowdular/sandbox": "0.6.5",
 		"@tsrx/prettier-plugin": "0.3.120",
 		"prettier": "3.6.2",
-		"flowdular": "0.6.3",
+		"flowdular": "0.6.5",
 		"rulesync": "16.21.0"
 	}
 }

package/template/default/platform/package.json

@@ -15,7 +15,7 @@
 		"@octanejs/vite-plugin": "0.2.1",
 		"octane": "0.9.1",
 		"pg": "8.23.0",
-		"@flowdular/sdk": "0.6.3"
+		"@flowdular/sdk": "0.6.5"
 	},
 	"devDependencies": {
 		"@octanejs/app-core": "0.1.1",