@authorbot/schemas 0.1.35 → 0.1.37

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 +70 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -9,6 +9,76 @@ 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.37
13
+
14
+ - **Cloudflare D1 can now apply the Phase 3B capability backfill.** The 0.1.36
15
+ form of migration `0013_phase11_capabilities_backfill.sql` used compound
16
+ `UNION ALL` projections inside a persistent compatibility view. Each catalog
17
+ exceeded D1's five-term compound-select limit, so upgraded books stopped
18
+ safely before deploying the new Worker. The corrected pending migration now
19
+ uses compact `VALUES` lookup tables while preserving the exact scope
20
+ sanitation, capability ordering, audit trail, and rollback guard
21
+ while staying within D1's limit. A Wrangler-backed regression applies the
22
+ complete migration chain in the same local D1 runtime used by Cloudflare's
23
+ tooling so this class of failure is caught before release.
24
+ - Version 0.1.36 is superseded by this hotfix. Books whose 0.1.36 publish
25
+ stopped at migration 0013 can upgrade normally to 0.1.37; Wrangler did not
26
+ record the failed migration, so the corrected file is applied on the next
27
+ publish before deployment. This release adds no new migration filename and
28
+ no book-format migration.
29
+
30
+ ## 0.1.36
31
+
32
+ - **Legacy agent-token rows now have a canonical capability projection.** D1
33
+ migration `0013_phase11_capabilities_backfill.sql` translates every
34
+ legacy-mode token after the v0.1.35 dual-writer release gate. Individual
35
+ books may safely skip straight from an older supported Worker. It leaves
36
+ `capability_mode` as `legacy`, keeps ordinary legacy scopes authoritative,
37
+ and does not change expiry or revocation state. Unknown and control-plane
38
+ scope names already stored are removed as an intentional authority reduction
39
+ and recorded in the audit trail; malformed legacy scope sets fail closed.
40
+ Historical mint replay bodies are updated to the corrected scopes without
41
+ rewriting the original audit event. A persistent database guard projects
42
+ safe old-Worker writes and rejects a later legacy write that still needs
43
+ scope sanitation, so a direct version skip or Worker rollback cannot reopen
44
+ a post-backfill gap or return a misleading success. The v0.1.36 Worker
45
+ sanitizes deprecated legacy mint requests before the write, so its response,
46
+ replay, mint audit, and stored row agree; the sanitation event preserves what
47
+ was removed.
48
+ - **Chapter editing now feels like the published manuscript.** Milkdown uses
49
+ the reading view's measure, type, color, spacing, and background, and the
50
+ site's CSP permits its inlined font without widening network font access.
51
+ Note, suggestion, and reply entry stays hidden for the whole edit handoff;
52
+ an in-progress draft is restored losslessly when editing closes, including
53
+ after a failed write or editor teardown.
54
+ - **Chapter history is a complete, responsive time machine.** The current
55
+ version stays on the reading page while the history rail starts with the
56
+ newest prior revision and loads the rest in the background. The pinned rail
57
+ has its own scroll, current and malformed cursor chains are bounded honestly,
58
+ and source events refresh without destroying the selected diff, keyboard
59
+ focus, or layout preference. Diffs use word-level matching for manuscript
60
+ paragraphs, omit line and hunk numbers, offer inline or side-by-side views
61
+ when space permits, and collapse to the normal reading measure on narrower
62
+ screens. Node local development now exposes the same contained, bounded Git
63
+ history reads as the deployed coordinator path.
64
+ - **Approved chapter discussions no longer look like pending votes.** Once a
65
+ chapter-wide comment is visible, its approve/reject/abstain control is gone;
66
+ maintainer comments continue to bypass moderation under every comment
67
+ policy.
68
+ - Frontend entry boundaries and lazy editor/diff loading remain, but compressed
69
+ byte ceilings are no longer release gates and Vite's chunk-size warning is
70
+ disabled. Bundle size is not a product requirement for this release.
71
+ - The authorization migration in this release is the Phase 3B backfill only.
72
+ It includes no book-format migration and does not retire legacy
73
+ authorization semantics, remove the legacy compatibility endpoint, or
74
+ remove legacy storage. The compatibility guard remains until Phase 3C,
75
+ which is separately gated by its compatibility and rollback window.
76
+ - Books already on 0.1.35 can run the ordinary `npx authorbot upgrade`. A book
77
+ on 0.1.34 or earlier needs one explicit
78
+ `npx --yes @authorbot/cli@0.1.36 upgrade --to 0.1.36`. After the resulting PR
79
+ is merged and the checkout is installed, ordinary `npx authorbot upgrade`
80
+ owns later handoffs automatically.
81
+
12
82
  ## 0.1.35
13
83
 
14
84
  - **Legacy agent-token requests now maintain the canonical projection.** The
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@authorbot/schemas",
3
- "version": "0.1.35",
3
+ "version": "0.1.37",
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",