create-githolon 0.7.0 → 0.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-githolon",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "type": "module",
   "description": "Scaffold a Nomos domain package: the starter domain + compile config + live e2e. `npm create githolon my-app`.",
   "license": "SEE LICENSE IN LICENSE.md",

package/template/domains/todo.ts

@@ -7,12 +7,9 @@
  */
 import {
   z, aggregate, t, Lww, AddWins, directive, create, instance, set, addToSet,
-  query, count, writeTuple, RelationTuple, relateSubject, relationTuplesByObject,
+  query, count, writeTuple, RelationTuple, relationTuplesByObject,
 } from "@githolon/dsl";
 
-// A todo is open or done. (There is no t.bool() — model a flag as a 2-value Lww enum.)
-const DONE = ["open", "done"] as const;
-
 // ── what we store ─────────────────────────────────────────────────────────────
 export const TodoList = aggregate("TodoList", {
   title: t.string().merge(Lww), // last writer wins
@@ -21,15 +18,10 @@ export const TodoList = aggregate("TodoList", {
 export const Todo = aggregate("Todo", {
   listId: t.string().merge(Lww),       // which list this todo is on (the query key)
   text: t.string().merge(Lww),         // last writer wins
-  done: t.enum(DONE).merge(Lww),       // last writer wins
+  done: t.bool(),                      // a flag — Lww by default; reads back a real boolean
   tags: t.set(t.string()).merge(AddWins), // concurrent taggers UNION — nobody's tag is lost
 });
 
-// Re-export the framework's Zanzibar tuple aggregate so its events fold into THIS
-// chain. relateSubject (an `.ensures(RelationTuple)` directive) is what marks the
-// tuple an ensured type, which shareList's tuple write below needs.
-export { RelationTuple, relateSubject };
-
 // ── what people do (directives PLAN ops; the sealed engine replays them) ────────
 export const createList = directive("createList")
   .creates(TodoList) // Nomos MINTS the id — callers never supply one
@@ -40,7 +32,7 @@ export const addTodo = directive("addTodo")
   .creates(Todo)
   .payload(z.object({ listId: z.string().min(1), text: z.string().min(1) }))
   .plan((p) => {
-    create(Todo).set("listId", p.listId).set("text", p.text).set("done", "open");
+    create(Todo).set("listId", p.listId).set("text", p.text).set("done", false);
     return [];
   });
 
@@ -49,11 +41,11 @@ export const renameTodo = directive("renameTodo")
   .payload(z.object({ todoId: z.string(), text: z.string().min(1) }))
   .plan((p) => [set(instance(Todo, p.todoId), "text", p.text)]);
 
-// The caller decides open↔done and rides it IN the payload (a plan is pure — no clock,
+// The caller decides done/not-done and rides it IN the payload (a plan is pure — no clock,
 // no random). Concurrent toggles are Lww: the later HLC wins, and both peers converge.
 export const toggleTodo = directive("toggleTodo")
   .mutates(Todo)
-  .payload(z.object({ todoId: z.string(), done: z.enum(DONE) }))
+  .payload(z.object({ todoId: z.string(), done: z.boolean() }))
   .plan((p) => [set(instance(Todo, p.todoId), "done", p.done)]);
 
 // addToSet is the ONLY additive write to an AddWins set (set() would overwrite).
@@ -77,9 +69,9 @@ export const shareList = directive("shareList")
 // ── what people read (auto-discovered by shape; routed to every peer) ───────────
 export const todosByList = query("todosByList").key("listId").returns(Todo);
 
-// An O(1) maintained tally: how many todos are still open, per list.
+// An O(1) maintained tally: how many todos are still open (done = false), per list.
 export const openTodosByList = count("openTodosByList")
-  .of(Todo).where((p) => p.field("done").eq("open")).by("listId");
+  .of(Todo).where((p) => p.field("done").eq(false)).by("listId");
 
 // The raw sharing tuples for a list — the audit surface (re-exported so it routes here).
 export { relationTuplesByObject };

package/template/nomos.package.mjs

@@ -1,7 +1,8 @@
 // The githolon-compile config: one package, one domain, one module file.
 // Read-side declarations (the query + the count) are auto-discovered from the
 // module's exports by shape — nothing to wire here. The framework RelationTuple
-// aggregate + its relationTuplesByObject query are pulled in by todo.ts's re-exports.
+// aggregate is auto-injected by shareList's `.ensures(RelationTuple)`; todo.ts only
+// re-exports the relationTuplesByObject query (the read side).
 // Building a Flutter app too? Add `dart: true` for the typed Dart frontend
 // (build/dart/) alongside the TS client.
 export default {

package/template/test/e2e.mts

@@ -73,7 +73,7 @@ ok("typed offline writes — createList + 2 addTodo, under the pulled law");
 const seeded = await app.todosByList({ listId });
 if (seeded.length !== 2) fail(`local query: expected 2 todos, got ${seeded.length}`);
 const t1 = seeded.find((row) => row.data.text === "Draft the deck")!.id;
-await app.toggleTodo({ todoId: t1, done: "done" });          // Lww enum — open ↔ done
+await app.toggleTodo({ todoId: t1, done: true });            // Lww boolean (t.bool)
 await app.tagTodo({ todoId: t1, tags: ["urgent", "q3"] });   // AddWins set
 ok(`read back a minted Todo id (${t1.slice(0, 16)}…) → toggled done + tagged`);