@authorbot/schemas 0.1.36 → 0.1.38

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +45 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -9,6 +9,51 @@ Every published package shares this version. A tag builds, tests, and publishes
9
9
  all of them together, so `@authorbot/cli@0.1.15` and `@authorbot/api@0.1.15` are
10
10
  always the same commit.
11
11
 
12
+ ## 0.1.38
13
+
14
+ - **Authorbot now has a complete local authoring mode.** `authorbot dev` runs
15
+ the real API and browser UI against a managed branch and persistent Git
16
+ worktree, with private SQLite state outside the book repository. It needs no
17
+ Cloudflare account or GitHub connection, and needs no network after the
18
+ packages are installed. Companion commands report status, print the private
19
+ starter agent environment, reset operational state without touching Git,
20
+ open a draft book pull request, and remove only worktrees Git can prove are
21
+ safe to clean up.
22
+ - **Local editing follows the repository instead of fighting it.** API reads
23
+ are pinned to committed `HEAD`, while the preview can show direct editor
24
+ saves immediately. API writes pause while the worktree is dirty or on the
25
+ wrong branch, and resume after an explicit forward-moving author commit.
26
+ Local maintainer sign-in uses a one-use bootstrap link, book-specific
27
+ cookies, a stable `local:` identity, and a private full-editor starter token.
28
+ - **The local browser loop is fast enough for Authorbot development.**
29
+ Astro/Vite serves the only browser origin and proxies the private loopback
30
+ API. Book and UI changes reload without throwing away SQLite or tokens, the
31
+ local toolbar reports branch and projection state, and a pending reload
32
+ waits when a form or editor has unsaved input. Backend source edits still
33
+ require restarting `authorbot dev`.
34
+ - Local authoring uses Node's built-in SQLite instead of a native module.
35
+ Authorbot's CLI and local runtime now require Node 22.13 or newer. Cloudflare
36
+ remains the hosted production runtime. This release has no book-format
37
+ migration and no new D1 migration.
38
+
39
+ ## 0.1.37
40
+
41
+ - **Cloudflare D1 can now apply the Phase 3B capability backfill.** The 0.1.36
42
+ form of migration `0013_phase11_capabilities_backfill.sql` used compound
43
+ `UNION ALL` projections inside a persistent compatibility view. Each catalog
44
+ exceeded D1's five-term compound-select limit, so upgraded books stopped
45
+ safely before deploying the new Worker. The corrected pending migration now
46
+ uses compact `VALUES` lookup tables while preserving the exact scope
47
+ sanitation, capability ordering, audit trail, and rollback guard
48
+ while staying within D1's limit. A Wrangler-backed regression applies the
49
+ complete migration chain in the same local D1 runtime used by Cloudflare's
50
+ tooling so this class of failure is caught before release.
51
+ - Version 0.1.36 is superseded by this hotfix. Books whose 0.1.36 publish
52
+ stopped at migration 0013 can upgrade normally to 0.1.37; Wrangler did not
53
+ record the failed migration, so the corrected file is applied on the next
54
+ publish before deployment. This release adds no new migration filename and
55
+ no book-format migration.
56
+
12
57
  ## 0.1.36
13
58
 
14
59
  - **Legacy agent-token rows now have a canonical capability projection.** D1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@authorbot/schemas",
3
- "version": "0.1.36",
3
+ "version": "0.1.38",
4
4
  "description": "Zod v4 schemas, inferred TypeScript types, and generated JSON Schemas for Authorbot book-repository artifacts (Phase 0 contract section 4)",
5
5
  "keywords": [
6
6
  "authorbot",