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