create-theokit 2.0.0 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-theokit",
3
- "version": "2.0.0",
3
+ "version": "3.0.0",
4
4
  "type": "module",
5
5
  "description": "Scaffold a new TheoKit project",
6
6
  "repository": {
@@ -14,13 +14,20 @@ tone instruction in this file quietly makes `usePersonality` do nothing. Tone be
14
14
 
15
15
  ## Why this file is here and not at the root
16
16
 
17
- On the SDK this project installs (`^4.52.1`, which resolves to a 4.x), `.theokit/THEO.md` is the
18
- **only** path a `THEO.md` is read from a copy at the project root is read by nothing, silently.
19
-
20
- `@theokit/sdk@5` adds a root `THEO.md` (`usetheokit/theokit-sdk#531`) at priority 55, so on that
21
- version both locations work and `.theokit/THEO.md` still wins a conflict. 5.x is currently published
22
- on the `next` channel only, so moving this file to the root would break it for anyone on the default
23
- install which is why the scaffold keeps it here.
17
+ This project installs `@theokit/sdk@^5.3.0`, where **both** locations work: 5.x added a root
18
+ `THEO.md` (`usetheokit/theokit-sdk#531`) at priority 55, and `.theokit/THEO.md` at 60 still wins a
19
+ conflict. The scaffold keeps the file here because it wins, not because the root is unreadable.
20
+
21
+ That reason is new. This paragraph used to say the template pinned `^4.52.1` where
22
+ `.theokit/THEO.md` was the **only** path read and a root copy was silently ignored and that 5.x
23
+ was published on the `next` channel only, so moving the file would break the default install. Both
24
+ halves expired: 5.5.0 is `latest`, and the template's pin moved to `^5.3.0` because every `.claude`
25
+ parity surface this framework advertises is absent from 4.x. A scaffold that hands a new project an
26
+ SDK delivering none of that, with nothing saying so, is the defect the pin change closes.
27
+
28
+ The floor is 5.3 rather than 5.0 because the framework's persistence barrel re-exports six names that
29
+ 5.0.0 does not have — measured with controls, 1 of 7 at 5.0.0 and 7 of 7 from 5.3.0 — so the range had
30
+ to name a version that can actually build it.
24
31
 
25
32
  Two more things worth knowing if you do move it once 5.x is stable:
26
33
 
@@ -16,9 +16,9 @@
16
16
  "typecheck": "tsc --noEmit"
17
17
  },
18
18
  "dependencies": {
19
- "theokit": "^0.65.0",
19
+ "theokit": "^0.66.0",
20
20
  "@theokit/agents": "^12.1.0",
21
- "@theokit/sdk": "^4.52.1",
21
+ "@theokit/sdk": "^5.3.0",
22
22
  "@theokit/ui": "^1.1.0",
23
23
  "@usetheo/ui": "^0.26.0",
24
24
  "lucide-react": "^0.469.0",