@authorbot/domain 0.1.25 → 0.1.27

package/CHANGELOG.md

@@ -1,7 +1,7 @@
 # Changelog
 
 What changed in each release, and why it mattered. Written for the person
-deciding whether to upgrade, not for the person who wrote the commit — so a
+deciding whether to upgrade, not for the person who wrote the commit - so a
 release that fixed something serious says what was broken and what it did to
 you, rather than naming the function that changed.
 
@@ -9,11 +9,28 @@ Every published package shares this version. A tag builds, tests, and publishes
 all of them together, so `@authorbot/cli@0.1.15` and `@authorbot/api@0.1.15` are
 always the same commit.
 
+## 0.1.27
+
+- **The reading site and author console have been redesigned together.** The
+  reader now has clearer book navigation, chapter context, responsive story
+  views, and exact inline annotation highlights. Authors get focused Work,
+  Settings, and Access consoles with honest conflict handling, accessible
+  controls, and account-aware navigation.
+- Outline, Timeline, and Characters now expose the book's planning structure
+  directly, including the planning method selected in `book.yml`.
+- No book-format migration or database migration is required for this release.
+
+## 0.1.26
+
+- Removed every em-dash and en-dash from the tool's output, docs, and code. No
+  behaviour change; the wizard, error messages, and generated files now use
+  plain hyphens.
+
 ## 0.1.25
 
 - **The collaborator skill.** `npx skills add JoeMattie/authorbot` installs a
-  skill that teaches an agent to contribute to an Authorbot book — the loop,
-  the safety rules, per-role guidance, and the full API reference — into Claude
+  skill that teaches an agent to contribute to an Authorbot book - the loop,
+  the safety rules, per-role guidance, and the full API reference - into Claude
   Code and any other supported agent tooling. Also installable as a Claude Code
   plugin (`/plugin marketplace add JoeMattie/authorbot`). The `agent` stage now
   points at it.
@@ -21,7 +38,7 @@ always the same commit.
 ## 0.1.24
 
 - **`collaborate` commits and pushes what it writes.** It used to ask you to do
-  it "when you are ready" — and until that push lands, the API cannot project
+  it "when you are ready" - and until that push lands, the API cannot project
   your book, so the settings page reports that it cannot read its own
   configuration, with nothing connecting the two.
 - **The agent stage stopped asking for a maintainer bearer token.** No author
@@ -29,7 +46,7 @@ always the same commit.
   credential from elsewhere. `AUTHORBOT_API_TOKEN` still works for that case,
   and everyone else is sent to the button on the settings page.
 - Declining an optional step no longer tells you to run that step "to
-  continue", which made every optional thing look unfinished — `upgrade` most
+  continue", which made every optional thing look unfinished - `upgrade` most
   of all, on a book far too new to need it.
 
 ## 0.1.23
@@ -44,7 +61,7 @@ always the same commit.
 - **You can create an agent token from your book's settings.** Until now
   nothing in Authorbot could make one: the API needs a maintainer session,
   which only a browser holds, and the settings page could list and revoke
-  tokens but not create them — while the setup wizard asked for a bearer token
+  tokens but not create them - while the setup wizard asked for a bearer token
   no author has ever been issued. The control sits under Agent tokens, shows
   the value once, and defaults to the narrowest scopes an agent needs to read
   chapters, claim work, and submit a draft.
@@ -53,7 +70,7 @@ always the same commit.
 
 - **Installing the GitHub App no longer lands you on a 404.** GitHub was asked
   to run its OAuth flow during installation, which redirected to a callback
-  that cannot exist yet — the Worker's config needs the installation id that
+  that cannot exist yet - the Worker's config needs the installation id that
   installing is in the middle of producing. It now returns you to your book's
   own site.
 - **The agent stage stopped asking for a credential nobody has.** It wanted "a
@@ -68,8 +85,8 @@ always the same commit.
 - **The GitHub App key was stored in a format the Worker cannot read.** GitHub's
   manifest hands back a PKCS#1 key; WebCrypto, which is all a Cloudflare Worker
   has, can only import PKCS#8. So every book reported its integration as
-  `invalid` and did no Git work at all — chapters could not be saved, the
-  projection never ran, settings could not read `book.yml` — with all three
+  `invalid` and did no Git work at all - chapters could not be saved, the
+  projection never ran, settings could not read `book.yml` - with all three
   credentials present and correct. **Books set up before this release need
   their GitHub App deleted and `collaborate` run again**, because the key was
   stored once and cannot be re-read.
@@ -81,7 +98,7 @@ always the same commit.
 
 ## 0.1.19
 
-- Spinners with an elapsed timer on the steps that take minutes — installing
+- Spinners with an elapsed timer on the steps that take minutes - installing
   the toolchain, waiting for a site to answer, checking the API. Silence for
   four minutes reads as a hang.
 - The mark is centred on the terminal's true width.
@@ -99,7 +116,7 @@ always the same commit.
 - **`npm install` failed for everyone who started the documented way.** npx
   exports its own configuration as `npm_config_*`, the wizard's `npm install`
   inherited it, and resolved against npx's cache directory instead of your
-  book — so the install failed and you were left without a
+  book - so the install failed and you were left without a
   `package-lock.json`, which both generated workflows refuse to run without. It
   worked fine for anyone running the built binary directly, which is why it
   looked like a problem with the machine.
@@ -113,10 +130,10 @@ always the same commit.
 - **`unpublish` and `teardown`.** `npx @authorbot/create unpublish` removes the
   Worker, the database and the GitHub App, leaving your repository and its
   history alone so `publish` can put the site back. `teardown` also deletes the
-  remote repository, then tells you what to type to remove the local copy — it
+  remote repository, then tells you what to type to remove the local copy - it
   never deletes files on your own disk.
 - **The wizard is drawn rather than printed**: boxed stage headings, an arrow
-  for steps, and check/triangle/cross for outcomes — each degrading to plain
+  for steps, and check/triangle/cross for outcomes - each degrading to plain
   ASCII under `NO_COLOR`, in a pipe, or on a dumb terminal.
 - **A changelog**, here and inside every published package.
 
@@ -124,7 +141,7 @@ always the same commit.
 
 - **The wizard can tell whether your book can actually save anything.** It used
   to finish by checking that the API refused an anonymous caller, which a
-  completely unusable deployment does just as correctly as a healthy one — see
+  completely unusable deployment does just as correctly as a healthy one - see
   0.1.14. New `GET /v1/health` reports whether the GitHub App is usable, and
   `collaborate` refuses to switch a book's collaboration controls on when the
   answer is no.
@@ -134,14 +151,14 @@ always the same commit.
 - **Collaboration never worked on any book this wizard created.** The Worker
   needs three GitHub App credentials and received two: the app id was read,
   used to poll for the installation, and then dropped. With one missing it does
-  no Git work at all — so chapters could not be saved, the projection never
+  no Git work at all - so chapters could not be saved, the projection never
   ran, and settings could not read the book's own `book.yml`, while every
   read-only page answered perfectly. If you set up a book before this release,
   re-run `create-authorbot collaborate`.
 - **You can sign out.** There was no way to. Two routes created a session and
   none ended one, so a reader on a shared machine stayed signed in until the
   cookie expired.
-- **An account strip in the site header** — sign in, sign out, and the way into
+- **An account strip in the site header** - sign in, sign out, and the way into
   Settings and the work queue. Previously a book with no chapters had no
   sign-in anywhere, and `/settings/` and `/work/` were linked from nowhere.
 - The API health check polls instead of judging on its first answer, which was
@@ -157,7 +174,7 @@ always the same commit.
 
 - **A book with collaboration on showed no sign-in and no annotations.**
   `book.yml` said annotations were public; the Worker was never told, so the
-  API refused every anonymous read — and the site gives up and renders nothing
+  API refused every anonymous read - and the site gives up and renders nothing
   when its first read fails, removing the very control that would have fixed
   it.
 
@@ -194,7 +211,7 @@ always the same commit.
 ## 0.1.7
 
 - **A successful deploy was reported as a failure** when the local resolver
-  still had the new hostname cached as non-existent — which the wizard's own
+  still had the new hostname cached as non-existent - which the wizard's own
   domain check made near-certain.
 - Every "run this to carry on" hint named `create-authorbot`, a binary `npx`
   never installs.
@@ -212,7 +229,7 @@ always the same commit.
 ## 0.1.5
 
 - Pointing the wizard at a directory that did not exist yet failed with a bare
-  ENOENT — including for the `directory: ./my-book` its own example config
+  ENOENT - including for the `directory: ./my-book` its own example config
   prints.
 - The pinned GitHub Actions moved off a deprecated line.
 

package/dist/annotation-policy.d.ts

@@ -1,5 +1,5 @@
 /**
- * Annotation policy (Phase 7 contract "Restricting") — who may write to a
+ * Annotation policy (Phase 7 contract "Restricting") - who may write to a
  * book, and whether what they write appears immediately.
  *
  * | Mode                | Who may write            | Appears                    |
@@ -36,7 +36,7 @@ export type AnnotationPolicy = (typeof ANNOTATION_POLICIES)[number];
  * The mode a book with no declared policy runs in: the Phase 2 behaviour,
  * unchanged. A deployment upgrading into Phase 7 must not find its book
  * suddenly writable by strangers, so the default is the restrictive end of the
- * progression that people were already on — not the permissive end, and not
+ * progression that people were already on - not the permissive end, and not
  * `locked` either, which would lock out the collaborators they already have.
  */
 export declare const DEFAULT_ANNOTATION_POLICY: AnnotationPolicy;
@@ -52,21 +52,21 @@ export type AnnotationPolicyDenialReason =
  | "locked"
 /**
  * Signed in and not a member, asking for something a non-member could never
- * do (voting, claiming, submitting) even in an open book — those are member
+ * do (voting, claiming, submitting) even in an open book - those are member
  * capabilities, and `open` widens commenting, not the work queue.
  */
  | "member-capability";
 /**
  * The write capabilities the policy arbitrates.
  *
- * `annotate` is the one the policy table is actually about — commenting and
+ * `annotate` is the one the policy table is actually about - commenting and
  * suggesting. The other three are member capabilities that `open` and
  * `approval-gated` do NOT widen to strangers: a book that welcomes comments
  * from the internet is not thereby handing the internet its governance votes
  * or its work queue.
  *
  * `locked` restricts all four, because "existing collaborators keep their
- * membership and their history — they simply cannot write until the policy
+ * membership and their history - they simply cannot write until the policy
  * opens again", and a vote that manufactures a work item is unambiguously a
  * write.
  */
@@ -83,7 +83,7 @@ export interface AnnotationPolicyRequest {
  * Decide whether the policy admits this write.
  *
  * This answers the policy question ONLY. Scope checks, freeze, the agent pause,
- * and rate limits are separate gates applied alongside it — a request must
+ * and rate limits are separate gates applied alongside it - a request must
  * satisfy all of them, and each refuses with its own problem type so the caller
  * can tell "the book is locked" from "the book is frozen" from "you are going
  * too fast".

package/dist/annotation-policy.js

@@ -1,5 +1,5 @@
 /**
- * Annotation policy (Phase 7 contract "Restricting") — who may write to a
+ * Annotation policy (Phase 7 contract "Restricting") - who may write to a
  * book, and whether what they write appears immediately.
  *
  * | Mode                | Who may write            | Appears                    |
@@ -39,7 +39,7 @@ export const ANNOTATION_POLICIES = [
  * The mode a book with no declared policy runs in: the Phase 2 behaviour,
  * unchanged. A deployment upgrading into Phase 7 must not find its book
  * suddenly writable by strangers, so the default is the restrictive end of the
- * progression that people were already on — not the permissive end, and not
+ * progression that people were already on - not the permissive end, and not
  * `locked` either, which would lock out the collaborators they already have.
  */
 export const DEFAULT_ANNOTATION_POLICY = "collaborators-only";
@@ -54,7 +54,7 @@ export function policyRequiresApproval(policy) {
  * Decide whether the policy admits this write.
  *
  * This answers the policy question ONLY. Scope checks, freeze, the agent pause,
- * and rate limits are separate gates applied alongside it — a request must
+ * and rate limits are separate gates applied alongside it - a request must
  * satisfy all of them, and each refuses with its own problem type so the caller
  * can tell "the book is locked" from "the book is frozen" from "you are going
  * too fast".
@@ -89,7 +89,7 @@ export function checkAnnotationPolicy(request) {
         }
         return ALLOWED;
     }
-    // collaborators-only — the Phase 2 behaviour, and the default.
+    // collaborators-only - the Phase 2 behaviour, and the default.
     if (isMember) {
         return ALLOWED;
     }

package/dist/annotation-state.d.ts

@@ -8,7 +8,7 @@ export type { AnnotationStatus };
  * section 4). `open` fans out; `rejected -> open` is the Phase 3 maintainer
  * reopen override (Phase 3 contract section 4); every other status is
  * terminal. The reanchor flow (`needs_reanchor -> open`) is intentionally not
- * legal yet — adding transitions later is additive.
+ * legal yet - adding transitions later is additive.
  */
 export declare const ANNOTATION_TRANSITIONS: Readonly<Record<AnnotationStatus, readonly AnnotationStatus[]>>;
 export declare function canTransitionAnnotation(from: AnnotationStatus, to: AnnotationStatus): boolean;

package/dist/annotation-state.js

@@ -6,7 +6,7 @@ export { ANNOTATION_STATUSES };
  * section 4). `open` fans out; `rejected -> open` is the Phase 3 maintainer
  * reopen override (Phase 3 contract section 4); every other status is
  * terminal. The reanchor flow (`needs_reanchor -> open`) is intentionally not
- * legal yet — adding transitions later is additive.
+ * legal yet - adding transitions later is additive.
  */
 export const ANNOTATION_TRANSITIONS = Object.freeze({
     open: [

package/dist/lease-token.d.ts

@@ -3,11 +3,11 @@ import { z } from "zod";
  * Lease-token FORMAT helpers only (Phase 4 contract section 2): parse and
  * shape-check, no crypto. Generating the 256-bit random secret, hashing it
  * (SHA-256), storing only the hash, and the constant-time compare are the
- * API layer's job — exactly the split used for agent tokens in `token.ts`.
+ * API layer's job - exactly the split used for agent tokens in `token.ts`.
  * Failure results carry a reason only and never echo any part of the value;
  * lease tokens are never logged.
  *
- * Format (resolved ambiguity — the contracts pin "opaque 256-bit token" but
+ * Format (resolved ambiguity - the contracts pin "opaque 256-bit token" but
  * no encoding): `authorbot_lease_` + 43 base64url chars, matching the agent
  * token secret encoding. The distinct prefix makes a leaked lease token
  * identifiable and unconfusable with an agent credential (an agent token is

package/dist/lease-token.js

@@ -3,11 +3,11 @@ import { z } from "zod";
  * Lease-token FORMAT helpers only (Phase 4 contract section 2): parse and
  * shape-check, no crypto. Generating the 256-bit random secret, hashing it
  * (SHA-256), storing only the hash, and the constant-time compare are the
- * API layer's job — exactly the split used for agent tokens in `token.ts`.
+ * API layer's job - exactly the split used for agent tokens in `token.ts`.
  * Failure results carry a reason only and never echo any part of the value;
  * lease tokens are never logged.
  *
- * Format (resolved ambiguity — the contracts pin "opaque 256-bit token" but
+ * Format (resolved ambiguity - the contracts pin "opaque 256-bit token" but
  * no encoding): `authorbot_lease_` + 43 base64url chars, matching the agent
  * token secret encoding. The distinct prefix makes a leaked lease token
  * identifiable and unconfusable with an agent credential (an agent token is

package/dist/lease.d.ts

@@ -18,7 +18,7 @@ export type IsoDurationParseResult = {
 };
 /**
  * Parse the ISO-8601 duration subset the contracts use (`PT30M`, `PT4H`,
- * `P1D`, combinations with integer designators; no years/months/weeks —
+ * `P1D`, combinations with integer designators; no years/months/weeks -
  * calendar units are ambiguous in milliseconds). Used to validate `LEASE_*`
  * env overrides at boot (Phase 4 contract section 2).
  */
@@ -66,7 +66,7 @@ export type LeaseInactiveReason = "expired" | "released" | "revoked";
  * Whether a lease still backs commands at `now`. Check order follows the
  * contract section 4 verification order ("not expired / not released"):
  * expired first, then released, then revoked. Used by renew, release, and
- * submission checks alike — an expired, released, or revoked lease can do
+ * submission checks alike - an expired, released, or revoked lease can do
  * nothing further (contract section 2: renewing an expired lease is a 409).
  */
 export declare function checkLeaseActive(lease: LeaseSnapshot, now: Date): Decision<LeaseInactiveReason>;
@@ -93,7 +93,7 @@ export type ClaimCheckResult = {
  * "none" is unambiguous). That combination is what an interrupted expiry or a
  * bare administrative revocation leaves behind, and treating it as
  * `lease-held` made such items permanently unclaimable, unreleasable, and
- * unsweepable — recoverable only by direct database surgery. Claiming
+ * unsweepable - recoverable only by direct database surgery. Claiming
  * self-heals it instead: `priorLeaseExpired` sends the caller down the
  * expire-then-claim path, whose compare-and-swap starts from `leased`.
  */
@@ -108,7 +108,7 @@ export type RenewCheckResult = {
  * renews; the new expiry is the current `expires_at` plus the renewal
  * duration ("extends by"), clamped to `max_expires_at`. When the lease
  * already sits at its max-total cap so no extension is possible, the renewal
- * is rejected with `max-total-exceeded` rather than succeeding as a no-op —
+ * is rejected with `max-total-exceeded` rather than succeeding as a no-op -
  * a partially clamped extension is still allowed. Verifying the presented
  * token against the stored hash happens before this in the API layer.
  */

package/dist/lease.js

@@ -26,7 +26,7 @@ export const LEASE_RENEWAL_PROMPT_BEFORE_MS = 5 * MS_PER_MINUTE;
 const ISO_DURATION_REGEX = /^P(?:(\d+)D)?(?:T(?:(\d+)H)?(?:(\d+)M)?(?:(\d+)S)?)?$/;
 /**
  * Parse the ISO-8601 duration subset the contracts use (`PT30M`, `PT4H`,
- * `P1D`, combinations with integer designators; no years/months/weeks —
+ * `P1D`, combinations with integer designators; no years/months/weeks -
  * calendar units are ambiguous in milliseconds). Used to validate `LEASE_*`
  * env overrides at boot (Phase 4 contract section 2).
  */
@@ -97,7 +97,7 @@ export function isLeaseExpired(lease, now) {
  * Whether a lease still backs commands at `now`. Check order follows the
  * contract section 4 verification order ("not expired / not released"):
  * expired first, then released, then revoked. Used by renew, release, and
- * submission checks alike — an expired, released, or revoked lease can do
+ * submission checks alike - an expired, released, or revoked lease can do
  * nothing further (contract section 2: renewing an expired lease is a 409).
  */
 export function checkLeaseActive(lease, now) {
@@ -125,7 +125,7 @@ export function checkLeaseActive(lease, now) {
  * "none" is unambiguous). That combination is what an interrupted expiry or a
  * bare administrative revocation leaves behind, and treating it as
  * `lease-held` made such items permanently unclaimable, unreleasable, and
- * unsweepable — recoverable only by direct database surgery. Claiming
+ * unsweepable - recoverable only by direct database surgery. Claiming
  * self-heals it instead: `priorLeaseExpired` sends the caller down the
  * expire-then-claim path, whose compare-and-swap starts from `leased`.
  */
@@ -146,7 +146,7 @@ export function checkWorkItemClaimable(status, activeLease, now) {
  * renews; the new expiry is the current `expires_at` plus the renewal
  * duration ("extends by"), clamped to `max_expires_at`. When the lease
  * already sits at its max-total cap so no extension is possible, the renewal
- * is rejected with `max-total-exceeded` rather than succeeding as a no-op —
+ * is rejected with `max-total-exceeded` rather than succeeding as a no-op -
  * a partially clamped extension is still allowed. Verifying the presented
  * token against the stored hash happens before this in the API layer.
  */

package/dist/overrides.d.ts

@@ -36,7 +36,7 @@ export declare const reopenSuggestionCommandSchema: z.ZodObject<{
 export type ReopenSuggestionCommand = z.infer<typeof reopenSuggestionCommandSchema>;
 /**
  * Override 4: force-create a work item bypassing the rule. `work_type` is not
- * part of the command — it resolves from the annotation scope exactly as
+ * part of the command - it resolves from the annotation scope exactly as
  * rule-created items do (Phase 3 contract section 3).
  */
 export declare const forceCreateWorkItemCommandSchema: z.ZodObject<{

package/dist/overrides.js

@@ -38,7 +38,7 @@ export const reopenSuggestionCommandSchema = z.strictObject({
 });
 /**
  * Override 4: force-create a work item bypassing the rule. `work_type` is not
- * part of the command — it resolves from the annotation scope exactly as
+ * part of the command - it resolves from the annotation scope exactly as
  * rule-created items do (Phase 3 contract section 3).
  */
 export const forceCreateWorkItemCommandSchema = z.strictObject({

package/dist/submission.d.ts

@@ -75,7 +75,7 @@ export type SubmissionBaseDenialReason = "base-revision-mismatch" | "base-hash-m
  * (contract section 4). Revision is checked before hash so the commoner
  * staleness cause surfaces first. Hash comparison here is not secret
  * material (both values are content hashes the client already holds), so a
- * plain compare is correct — constant-time treatment is for lease tokens.
+ * plain compare is correct - constant-time treatment is for lease tokens.
  */
 export declare function checkSubmissionBase(bundle: {
     readonly baseRevision: number;

package/dist/submission.js

@@ -70,7 +70,7 @@ export const contentHashSchema = z
     .regex(CONTENT_HASH_REGEX, "must be 'sha256:' followed by 64 lowercase hex characters");
 /**
  * Replacement content: CRLF folded to LF (matching chapter storage) but NOT
- * trimmed — leading/trailing whitespace is meaningful in a range
+ * trimmed - leading/trailing whitespace is meaningful in a range
  * replacement. Emptiness is a per-type rule handled in the command schema:
  * an empty `range_replacement` is a deletion and legal; block and chapter
  * replacements must be non-empty.
@@ -118,7 +118,7 @@ export const submitWorkCommandSchema = z
  * (contract section 4). Revision is checked before hash so the commoner
  * staleness cause surfaces first. Hash comparison here is not secret
  * material (both values are content hashes the client already holds), so a
- * plain compare is correct — constant-time treatment is for lease tokens.
+ * plain compare is correct - constant-time treatment is for lease tokens.
  */
 export function checkSubmissionBase(bundle, submission) {
     if (submission.baseRevision !== bundle.baseRevision) {

package/dist/token.d.ts

@@ -22,7 +22,7 @@ export type AgentTokenParseResult = {
 };
 /**
  * Shape-check a presented credential and split off the secret part (which the
- * API layer hashes for lookup). Failure results carry a reason only — never
+ * API layer hashes for lookup). Failure results carry a reason only - never
  * any fragment of the presented value.
  */
 export declare function parseAgentToken(value: string): AgentTokenParseResult;

package/dist/token.js

@@ -19,7 +19,7 @@ export function isAgentTokenFormat(value) {
 }
 /**
  * Shape-check a presented credential and split off the secret part (which the
- * API layer hashes for lookup). Failure results carry a reason only — never
+ * API layer hashes for lookup). Failure results carry a reason only - never
  * any fragment of the presented value.
  */
 export function parseAgentToken(value) {

package/dist/vote.d.ts

@@ -15,7 +15,7 @@ export declare const voteValueSchema: z.ZodEnum<{
     abstain: "abstain";
 }>;
 export type VoteValue = z.infer<typeof voteValueSchema>;
-/** `PUT .../annotations/{annotationId}/vote` — route param + body merged. */
+/** `PUT .../annotations/{annotationId}/vote` - route param + body merged. */
 export declare const castVoteCommandSchema: z.ZodObject<{
     annotationId: z.ZodString;
     value: z.ZodEnum<{
@@ -25,7 +25,7 @@ export declare const castVoteCommandSchema: z.ZodObject<{
     }>;
 }, z.core.$strict>;
 export type CastVoteCommand = z.infer<typeof castVoteCommandSchema>;
-/** `DELETE .../annotations/{annotationId}/vote` — the command is the route param. */
+/** `DELETE .../annotations/{annotationId}/vote` - the command is the route param. */
 export declare const clearVoteCommandSchema: z.ZodObject<{
     annotationId: z.ZodString;
 }, z.core.$strict>;
@@ -33,8 +33,8 @@ export type ClearVoteCommand = z.infer<typeof clearVoteCommandSchema>;
 export type VoteDenialReason = "not-a-suggestion";
 /**
  * Suggestion-only guard (contract section 2: votes on comments → 422). Votes
- * stay legal after `open` — sticky decisions require tracking vote changes on
- * `work_item_created` annotations (contract section 4) — so annotation status
+ * stay legal after `open` - sticky decisions require tracking vote changes on
+ * `work_item_created` annotations (contract section 4) - so annotation status
  * is deliberately not checked here; `votes:write` scope enforcement is the
  * API layer's (`requireScope`).
  */

package/dist/vote.js

@@ -10,19 +10,19 @@ import { ALLOWED, denied } from "./decision.js";
 /** Vote values (contract section 2; mirrors `authorbot.instance/v1` `votes.values`). */
 export const VOTE_VALUES = ["approve", "reject", "abstain"];
 export const voteValueSchema = z.enum(VOTE_VALUES);
-/** `PUT .../annotations/{annotationId}/vote` — route param + body merged. */
+/** `PUT .../annotations/{annotationId}/vote` - route param + body merged. */
 export const castVoteCommandSchema = z.strictObject({
     annotationId: uuidv7Schema,
     value: voteValueSchema,
 });
-/** `DELETE .../annotations/{annotationId}/vote` — the command is the route param. */
+/** `DELETE .../annotations/{annotationId}/vote` - the command is the route param. */
 export const clearVoteCommandSchema = z.strictObject({
     annotationId: uuidv7Schema,
 });
 /**
  * Suggestion-only guard (contract section 2: votes on comments → 422). Votes
- * stay legal after `open` — sticky decisions require tracking vote changes on
- * `work_item_created` annotations (contract section 4) — so annotation status
+ * stay legal after `open` - sticky decisions require tracking vote changes on
+ * `work_item_created` annotations (contract section 4) - so annotation status
  * is deliberately not checked here; `votes:write` scope enforcement is the
  * API layer's (`requireScope`).
  */

package/dist/work-item-lifecycle.d.ts

@@ -5,7 +5,7 @@ import { type Decision, type Denied } from "./decision.js";
  * Phase 3 gate lifted (Phase 4 contract sections 2, 4, 5). The graph itself
  * has been declared since Phase 3 (`WORK_ITEM_TRANSITIONS`); this module
  * adds the executable, trigger-labelled form. `transitionWorkItem` (the
- * Phase 3-gated function) is left untouched for compatibility — Phase 4
+ * Phase 3-gated function) is left untouched for compatibility - Phase 4
  * call sites use `transitionWorkItemPhase4` / `applyWorkItemTrigger`.
  */
 /**

package/dist/work-item-lifecycle.js

@@ -6,7 +6,7 @@ import { WORK_ITEM_TRANSITIONS, canTransitionWorkItem } from "./work-item-state.
  * Phase 3 gate lifted (Phase 4 contract sections 2, 4, 5). The graph itself
  * has been declared since Phase 3 (`WORK_ITEM_TRANSITIONS`); this module
  * adds the executable, trigger-labelled form. `transitionWorkItem` (the
- * Phase 3-gated function) is left untouched for compatibility — Phase 4
+ * Phase 3-gated function) is left untouched for compatibility - Phase 4
  * call sites use `transitionWorkItemPhase4` / `applyWorkItemTrigger`.
  */
 /**

package/dist/work-item-state.d.ts

@@ -5,7 +5,7 @@ export type { WorkItemStatus };
 /**
  * Work-item state machine (design section 9.5). The full transition graph is
  * declared so Phase 4 is additive data, but Phase 3 stops at `ready` (Phase 3
- * contract section 1: claims/leases/submissions are out of scope) — the only
+ * contract section 1: claims/leases/submissions are out of scope) - the only
  * transition that may actually execute is `ready -> cancelled` (maintainer
  * cancel). Every other graph edge is phase-gated: legal in the design, denied
  * at runtime with `phase-not-enabled` until Phase 4 lifts the gate.

package/dist/work-item-state.js

@@ -4,7 +4,7 @@ export { WORK_ITEM_STATUSES };
 /**
  * Work-item state machine (design section 9.5). The full transition graph is
  * declared so Phase 4 is additive data, but Phase 3 stops at `ready` (Phase 3
- * contract section 1: claims/leases/submissions are out of scope) — the only
+ * contract section 1: claims/leases/submissions are out of scope) - the only
  * transition that may actually execute is `ready -> cancelled` (maintainer
  * cancel). Every other graph edge is phase-gated: legal in the design, denied
  * at runtime with `phase-not-enabled` until Phase 4 lifts the gate.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@authorbot/domain",
-  "version": "0.1.25",
+  "version": "0.1.27",
   "description": "Pure domain logic for Authorbot: role/scope authorization, annotation and Git-operation state machines, command validators, and token/session value rules (Phase 2 contract section 3)",
   "keywords": [
     "authorbot",
@@ -40,7 +40,7 @@
   ],
   "dependencies": {
     "zod": "^4.0.0",
-    "@authorbot/schemas": "0.1.25"
+    "@authorbot/schemas": "0.1.27"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",