@danieljvdm/dev-kit 0.11.1 → 0.11.3

package/README.md

@@ -376,8 +376,8 @@ install, runs `dev-kit apply --locked`, and only then runs custom preparation,
 formatting, linting, tests, and typechecking. Its default typecheck command is
 `vp run typecheck`; `workflow.typecheck` replaces it. Vite+ maps install flags
 to the detected package manager. The template installs the consumer's declared
-Bun version and pins exact `setup-bun` and `setup-vp` releases; the latter's
-`v1` tag is frozen. Keep both current with Renovate or Dependabot. Existing
+Bun version, follows the maintained `setup-bun@v2` tag, and names the current
+`setup-vp` release because that action's `v1` tag is frozen. Existing
 workflows remain user-owned until their rendered content matches exactly—Dev
 Kit never merges YAML. See the primary
 [`setup-vp` versioning guidance](https://github.com/voidzero-dev/setup-vp#versioning),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danieljvdm/dev-kit",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "private": false,
   "description": "Declarative project development toolkit with portable agent skills.",
   "license": "MIT",

package/skills/dev-kit/SKILL.md

@@ -146,9 +146,9 @@ and `workflow.typecheck`; treat these commands as trusted manifest input.
 
 The workflow must use one frozen, script-suppressed install, then locked Dev Kit
 convergence before preparation or checks. Set up Bun from the consumer's
-`packageManager` or `engines.bun` declaration before Vite+ setup. Keep both
-`setup-bun` and `setup-vp` pinned to reviewed release commits—the `setup-vp`
-`v1` tag is frozen—and let Vite+ resolve the consumer's compatible locked
+`packageManager` or `engines.bun` declaration before Vite+ setup. Follow the
+maintained `setup-bun` major tag, name an explicit `setup-vp` release because
+its `v1` tag is frozen, and let Vite+ resolve the consumer's compatible locked
 version.
 
 ## Ownership and conflicts

package/skills/effect-ts/SKILL.md

@@ -110,7 +110,7 @@ When the task touches one of these areas, consult the matching guide before impl
   values, time zones, DST-safe arithmetic, formatting, Date interoperability,
   and deterministic `TestClock` tests
 - `./references/guide-atom-data-fetching.md` for the core Effect Atom HTTP
-  data-fetching workflow and ownership rules
+  data-fetching workflow, React hook choice, and action-lifetime ownership rules
 - `./references/atom-cache-lifecycle.md` for Effect Atom registry scope,
   runtime memoization, families, TTL, SWR, polling, and aggregation resets
 - `./references/atom-http-and-invalidation.md` for `AtomHttpApi.Service`,

package/skills/effect-ts/references/atom-cache-lifecycle.md

@@ -6,6 +6,12 @@
 
 Place one provider around the client application subtree that should share data. Nested or route-local providers create separate caches.
 
+### React mounts and registry disposal
+
+`useAtomValue` keeps an atom active through its value subscription. `useAtomSet` and `useAtomRefresh` mount an atom through a React effect, while `useAtom` combines one value subscription with a setter. Use the combined hook when one component reads and writes the same atom; composing `useAtomValue` and `useAtomSet` adds a second mount and obscures which lifetime owns the work.
+
+Unmount releases only that hook's subscription or mount. The registry removes a node only after it has no remaining consumers and its idle TTL permits removal. Node disposal runs registered finalizers, including cancellation of interruptible Effect work. Therefore component unmount, registry eviction, and `Atom.Interrupt` are distinct events; do not use an unconditional interrupt write as a substitute for releasing a React mount.
+
 An atom runtime and a registry solve different problems:
 
 - the registry stores atom nodes, values, subscriptions, idle timers, and finalizers;

package/skills/effect-ts/references/atom-http-and-invalidation.md

@@ -51,6 +51,10 @@ await mutate({
 
 The mutation's `reactivityKeys` are invalidated only after the request succeeds. Failed mutations do not invalidate. Keep navigation, toasts, dialog closure, and optimistic UI at the action owner; keep shared server-state refresh in reactivity keys.
 
+If the component also renders the mutation result, use `useAtom(updateProject)` instead of pairing `useAtomValue` with `useAtomSet`. A module-scoped mutation atom is shared registry state, so an unconditional cleanup write of `Atom.Interrupt` can cancel work owned by another consumer and publishes an interrupted failure.
+
+Keep a multi-step mutation sequence in an owner that lives for the whole sequence. When navigation can unmount the initiating route after one request succeeds, a component-owned sequential fan-out can leave a partially completed operation. Use one stable workflow atom or service when client ownership is sufficient; use one server-side command or durable workflow when completion must survive browser navigation or disconnects.
+
 ## Use one key vocabulary
 
 Array keys represent independent keys. Record keys support hierarchical broad-plus-entity invalidation:

package/skills/effect-ts/references/atom-testing.md

@@ -56,6 +56,10 @@ Prefer the installed test APIs over invented helpers or matchers. The upstream E
 3. Run a failed mutation; assert no invalidation.
 4. Assert cleanup removes invalidation handlers after query disposal.
 
+### React Strict Mode and action ownership
+
+Use a React integration test when hook cleanup or action ownership is part of the behavior. Render the owner inside `StrictMode` and assert the development setup-cleanup replay does not write `Atom.Interrupt` or publish an interrupted failure before an explicit cancellation. When an action spans multiple requests, unmount during the sequence and prove the chosen policy: either the stable owner completes every step, or an explicit cancellation interrupts it intentionally. If the atom is shared, also prove unmounting one consumer does not cancel work still owned by another.
+
 ### Aggregate stability
 
 Mount a route atom that uses `AsyncResult.all`, resolve every input, unmount, and remount inside the retention window. Assert the aggregate never returns to `Initial`. Then let one input expire and prove the aggregate reset is caused by that input, not the retained queries.

package/skills/effect-ts/references/guide-atom-data-fetching.md

@@ -23,6 +23,22 @@ Model server data as stable atoms owned outside React renders. Give the applicat
 - Ensure every input to a route-level `AsyncResult.all` has stable atom identity and compatible retention. One newly allocated or immediately evicted input returns to `Initial` and makes the whole aggregate appear reset even when the other inputs remain cached.
 - Do not describe manual refresh or polling as freshness caching. Refresh is forceful; `staleTime` only gates SWR's automatic mount/focus decisions.
 
+## React hooks and action lifetime
+
+Choose the hook that expresses the component's ownership:
+
+- `useAtomValue(atom)` subscribes for rendering without returning a setter;
+- `useAtomSet(atom)` mounts a writable atom and returns a setter without rendering from its value;
+- `useAtom(atom)` subscribes and returns a setter when the same component both renders and writes the atom.
+
+Do not pair `useAtomValue(atom)` with `useAtomSet(atom)` for the same atom in one component. The split form creates both a value subscription and a separate mount. Use `useAtom(atom)` instead. Calling an `Atom.family` directly with a stable primitive during render already returns the stable family member; a surrounding `useMemo` is not needed merely to preserve atom identity.
+
+The React hooks release their subscriptions and mounts when their component lifetime ends. Registry node removal then follows the atom's idle TTL and remaining consumers, and node disposal runs the atom lifetime finalizers. Do not confuse hook cleanup, idle retention, and operation cancellation: another consumer or a nonzero TTL can intentionally keep the node and its work alive after one component unmounts.
+
+Do not add a cleanup-only effect such as `useEffect(() => () => set(Atom.Interrupt), [set])` merely to mirror component unmount. `Atom.Interrupt` is a write that publishes an interrupted `AsyncResult.Failure`, not a passive release function. The cleanup also runs on dependency changes and during React Strict Mode's development effect replay, and it can interrupt work still owned by another consumer. Use `Atom.Interrupt` for an explicit user cancellation or a deliberately scoped cancellation policy, and test that ownership under Strict Mode.
+
+Decide whether an action must survive its initiating component before choosing its owner. A sequential client fan-out can partially complete if route unmount disposes its owner after earlier mutations succeed but before later ones start. If the whole sequence must be durable, move it to a stable workflow owner or one server-side command instead of relying on a route component's hook lifetime.
+
 ## Completion check
 
-Confirm one registry boundary, stable atom identity, deliberate TTL/staleness/polling values, matching query and mutation keys, SSR-safe browser access, and tests for every lifecycle behavior changed.
+Confirm one registry boundary, stable atom identity, deliberate TTL/staleness/polling values, matching query and mutation keys, an intentional React hook and action lifetime, SSR-safe browser access, and tests for every lifecycle behavior changed.

package/src/oxlint.js

@@ -24,7 +24,7 @@ export const recommendedOxlintConfig = {
     "import/default": "off",
     "import/namespace": "off",
     "import/no-cycle": "error",
-    "import/no-duplicates": "error",
+    "import/no-duplicates": ["error", { preferInline: true }],
     "import/no-self-import": "error",
     "react/exhaustive-deps": "error",
     "react/rules-of-hooks": "error",
@@ -38,7 +38,10 @@ export const recommendedOxlintConfig = {
       },
       { blankLine: "always", prev: "*", next: "return" },
     ],
-    "typescript/consistent-type-imports": "error",
+    "typescript/consistent-type-imports": [
+      "error",
+      { fixStyle: "inline-type-imports", prefer: "type-imports" },
+    ],
     "typescript/no-floating-promises": "off",
     "typescript/no-explicit-any": "error",
     "typescript/no-misused-spread": "off",

package/src/oxlint.ts

@@ -27,7 +27,7 @@ export const recommendedOxlintConfig = {
     "import/default": "off",
     "import/namespace": "off",
     "import/no-cycle": "error",
-    "import/no-duplicates": "error",
+    "import/no-duplicates": ["error", { preferInline: true }],
     "import/no-self-import": "error",
     "react/exhaustive-deps": "error",
     "react/rules-of-hooks": "error",
@@ -41,7 +41,10 @@ export const recommendedOxlintConfig = {
       },
       { blankLine: "always", prev: "*", next: "return" },
     ],
-    "typescript/consistent-type-imports": "error",
+    "typescript/consistent-type-imports": [
+      "error",
+      { fixStyle: "inline-type-imports", prefer: "type-imports" },
+    ],
     "typescript/no-floating-promises": "off",
     "typescript/no-explicit-any": "error",
     "typescript/no-misused-spread": "off",

package/templates/vite-plus/github-actions-check.yml

@@ -24,12 +24,10 @@ jobs:
 
       # setup-bun resolves the consumer's packageManager or engines.bun version.
       - name: Set up Bun
-        uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6 # setup-bun action v2.2.0
+        uses: oven-sh/setup-bun@v2
 
-      # setup-vp's v1 tag is frozen. Keep this v1.16.1 commit current with
-      # Renovate or Dependabot so fixes arrive through reviewed pull requests.
       - name: Set up Vite+ and install dependencies
-        uses: voidzero-dev/setup-vp@143f5f385f39b1b753ffed1a01ad443811855c8b # v1.16.1
+        uses: voidzero-dev/setup-vp@v1.16.1
         with:
           # Vite+ version intentionally resolves from the consumer manifest/lock.
           node-version: "24"