openwriter 0.35.0 → 0.35.2

package/dist/plugins/authors-voice/skill/docs/api/tools.md

@@ -0,0 +1,102 @@
+# API Reference
+
+## REST Endpoints (recommended)
+
+All endpoints require `Authorization: Bearer $AV_API_KEY`. Base URL: `https://api.authors-voice.com`
+
+### Core Skill Endpoints
+
+**Get voice profile** — full linguistic fingerprint (6 categories + sentence distribution):
+```bash
+curl -s https://api.authors-voice.com/api/voice/profiles/default \
+  -H "Authorization: Bearer $AV_API_KEY"
+# Optional: ?format=detailed for profile ID + summary
+```
+
+**Apply voice** — rewrite content in the author's voice:
+```bash
+curl -s -X POST https://api.authors-voice.com/api/voice/apply \
+  -H "Authorization: Bearer $AV_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"content": "text to rewrite", "mode": "rewrite", "inputType": "ai", "category": "x"}'
+```
+
+### Additional REST Endpoints
+
+| Endpoint | Method | Purpose |
+|----------|--------|---------|
+| `/api/voice/profiles` | GET | List profiles with counts |
+| `/api/voice/profiles/:profileId` | GET | Full voice profile (use `default` for default) |
+| `/api/voice/apply` | POST | Rewrite content in author's voice |
+| `/api/voice/setup` | POST | Analyze samples and build voice profile |
+| `/api/voice/content` | GET | List writing samples (query: profileId, category) |
+| `/api/voice/content` | POST | Upload content chunks |
+| `/api/voice/content/bulk` | POST | Bulk upload documents |
+| `/api/voice/content/:docId` | PATCH | Update doc metadata |
+| `/api/voice/content/:docId` | DELETE | Delete document |
+| `/api/voice/anchor/derive` | POST | Derive a voice anchor from pasted prose |
+| `/api/voice/anchor` | GET/PUT/DELETE | Read / persist / clear the voice anchor |
+| `/api/voice/usage` | GET | Usage stats |
+
+---
+
+## MCP Protocol (alternative)
+
+For MCP-compatible clients, all tools are also available via JSON-RPC POST:
+
+```bash
+curl -s -X POST "https://api.authors-voice.com/api/voice/mcp" \
+  -H "Authorization: Bearer $AV_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"TOOL_NAME","arguments":{...}}}'
+```
+
+---
+
+## Available Tools (12)
+
+### Content Import (3 tools)
+
+| Tool | Description |
+|------|-------------|
+| `import_from_url` | Import from any public URL (Medium, Substack, WordPress, .md/.txt). Args: `url`, `categories[]`, `authenticity`. |
+| `bulk_import` | Import multiple docs (max 50). Each item: `{url}` or `{content, docId}` + `categories[]`. Global `authenticity`. |
+| `upload_content` | Upload raw markdown. **One-click ergonomics**: `profileId` is optional — omit it and the server auto-creates/resolves a default profile. `content` can be raw text (server chunks on blank lines) instead of pre-split `chunks[]`, so the minimal payload is `{docId, content}`. Re-uploading the same `docId` replaces (idempotent). This is the contract the OpenWriter filetree right-click ingestion posts against. |
+
+### Voice Profiles (3 tools)
+
+| Tool | Description |
+|------|-------------|
+| `list_profiles` | List voice profiles, categories, and document counts. Each profile also carries `hasAnchor` (bool) and `anchorAuthors` (the reference authors behind the anchor), so callers can tell which profiles carry an anchor without a per-profile GET. No args. |
+| `get_voice_profile` | Get full voice guidelines — 6 linguistic categories + sentence stats. Use before writing to understand the author's patterns. Optional `profileId`. |
+| `setup_voice` | Analyze samples → create/update voice profile. Args: `profileName`, optional `forceReanalyze`. Call after importing content. |
+
+### Voice Anchor (1 tool)
+
+| Tool | Description |
+|------|-------------|
+| `set_voice_anchor` | Derive and persist a voice anchor from pasted reference prose. The anchor is V1's lead voice signal — injected ahead of sample retrieval in `rewrite`/`generate` and the OpenWriter editor path. REST equivalents: `POST /api/voice/anchor/derive`, `GET/PUT/DELETE /api/voice/anchor`. |
+
+### Voice Application (2 tools)
+
+| Tool | Description |
+|------|-------------|
+| `rewrite` | Rewrite existing content in the author's voice. Modes: `rewrite`, `shrink`, `expand`, `custom`. Supports `contextBefore`/`contextAfter`, `inputType`, `category`. |
+| `generate` | Generate NEW content in author's voice. Args: `instruction`, optional `query` (topic for retrieval), `contextBefore`/`contextAfter`, `category`, `targetWords`. |
+
+**rewrite parameters**: `content`, `mode`, `contextBefore`, `contextAfter`, `category`, `inputType` (human/ai/ai-assisted), `targetWords` (max 2000), `format` (markdown/plaintext).
+
+**inputType** controls how aggressively the rewrite treats the input:
+- `human` — Author's own writing. Preserve word choices and quirks, only polish flow/grammar.
+- `ai` — Generic AI content. Discard phrasing entirely, rewrite from scratch using voice samples.
+- `ai-assisted` (default) — Mixed authorship. Preserve passages matching the author's voice, rewrite generic/formulaic parts.
+
+**generate note**: `query` is optional — describes what content is ABOUT for better voice retrieval. When omitted, context + instruction are used for retrieval.
+
+### Content Management (3 tools)
+
+| Tool | Description |
+|------|-------------|
+| `list_content` | List writing samples with chunk counts. Optional `category` filter. |
+| `update_content` | Retag a doc. Args: `docId`, `categories[]`, `authenticity`. |
+| `delete_content` | Permanently delete a doc and its chunks. Args: `docId`. |

package/dist/plugins/authors-voice/skill/docs/api/troubleshooting.md

@@ -0,0 +1,7 @@
+# Troubleshooting
+
+**"Unauthorized"** — Check `AV_API_KEY` is set and starts with `av_live_`.
+
+**"profileId query parameter is required"** — Some REST endpoints need profileId. For MCP tools, omit profileId to use the default profile.
+
+**Empty document list** — Connection is active but no documents match. Try without a query filter.

package/dist/plugins/authors-voice/skill/docs/apply-protocol-deep.md

@@ -0,0 +1,191 @@
+# Apply Protocol — Deep Reference
+
+Loaded when scoping a brief (Apply step 4) or running cross-section coherence review (Apply step 8). Not in context for routing or other turns.
+
+## Step 4 — Writing the TASK brief
+
+Promoted to `SKILL.md` Apply Protocol step 4. The load-bearing rules (commitments-only default, never meta-references, COMMITMENTS as quasi-verbatim, read-prior-integrated-sections, preservation scope, cadence prescription) live there. This doc holds the edge-case templates and minion taxonomy below.
+
+## Writing minion taxonomy
+
+| Minion | Scope | Input | Output | When fires |
+|---|---|---|---|---|
+| **Apply** | Generative writing | Commitments + voice + context SUMMARIES (no source prose) | Fresh prose | Initial drafts. Also small reframes when audit prescribes a structural fix (audit's prescription becomes the commitment). |
+| **Rewrite** | Generative writing against updated commitments WITH context awareness | Updated commitments + voice + context layers (summary of preceding + key-term glossary + adjacent seam paragraphs as orientation-only) + cadence prescription. NO source prose for content being written. | Fresh prose | Beat Map commitments changed; surrounding prose is acceptable and should be preserved. Apply brief + context awareness layers. |
+
+Plus **Blinder Audit** (Step 8b — paragraph-level substance duplication, critic only) and **Anchor Iteration** (Step 10 — final polish, channels voice anchors as panel, iterates to 90/100; see `anchor-iteration.md`).
+
+### Editor's classification job after Audit fires
+
+Each finding routes to one of three paths:
+- **Editor direct (no minion)** — cuts, swaps, reorders, sentence-level surgical patches. Per FIRM RULE 1 carve-out.
+- **Rewrite Minion** — paragraph's SUBSTANCE needs to change (structurally redundant with another, or mission needs to shift). Compression alone produces thin output.
+- **Apply Minion (small)** — audit prescribes a specific reframe of a small span and new prose is needed (e.g., "reframe opening sentence to acknowledge pivot from X to Y"). Audit's prescription becomes the commitment.
+
+Classification rule: **before flagging anything for a minion, ask "is this a SHAPE problem or a SUBSTANCE problem?"** Different work needed → Rewrite or Cut. New prose into a small span → small Apply. Surgical word/sentence work on existing prose → editor direct.
+
+## Rewrite Minion
+
+The Rewrite Minion IS the Apply Minion fired with context awareness. The brief shape preserves Apply's no-source-prose-ceiling property (minion brings its own moves) while adding context layers needed to flow into surrounding prose.
+
+### Validated brief shape
+
+```
+[Voice profile: anchor, NEVER rules, fingerprints, stats, coined terms, examples]
+
+---
+
+TASK:
+
+PROJECT: [1-paragraph context — what the doc is, what the section does]
+
+CONTEXT — what's already established in the surrounding prose:
+- [Summary of preceding section as bullets — what was named, what was claimed, what threads are live. NOT raw prose. 5-10 bullets.]
+
+KEY TERMS already named (available for callback if useful):
+[Glossary list — coined terms, named concepts, distinctive phrasings the prose has established]
+
+IMMEDIATELY PRECEDING PARAGRAPH (for seam continuity ONLY; do NOT mirror its cadence):
+[Full paragraph verbatim — 1 only]
+
+IMMEDIATELY FOLLOWING PARAGRAPH (for seam continuity ONLY; do NOT mirror its cadence):
+[Full paragraph verbatim — 1 only]
+
+COMMITMENT(S) — what your new content must land in the reader:
+[Outcome statement(s) per beat]
+
+CADENCE PRESCRIPTION (per paragraph):
+[Explicit rhythm direction — open with X, build with Y, close with Z. Mandatory.]
+
+LENGTH: [target word count]
+
+Return prose only. No commentary. No headers. No beat labels.
+```
+
+The two seam paragraphs are full prose (minion needs flow continuity at the join), flagged explicitly as orientation-only. This avoids the source-prose ceiling because the task is "write fresh content that flows from / into these" rather than "match this cadence." **Framing matters more than presence.**
+
+### Why these elements
+
+- FULL adjacent seam paragraphs flagged "orientation only — do NOT mirror cadence" — flow continuity without ceiling
+- SUMMARIES of preceding section (bullets, not raw prose) + key-term glossary — document-scale awareness
+- OMITTING source prose for content being written — preserves no-ceiling property
+- INCLUDING explicit cadence prescription per paragraph — mandatory; short calls need cadence MORE, not less
+
+### Scope
+
+Works at any scope: paragraph-level (1 new paragraph), section-level (3-5 paragraphs), beat-level (full beat regeneration). Pick by what changed in commitments — one beat's outcome → regenerate one paragraph; chapter-arc beat's whole outcome shape → regenerate the whole beat; multiple beats → batch per chapter-arc beat.
+
+### Preserving specific lines from existing prose
+
+List them as MUST-APPEAR-VERBATIM in commitments (Apply's "selective lifts" mode). Rare — usually the writer's training data brings stronger lines than the existing prose anyway.
+
+### Audit follow-up MANDATORY
+
+Rewrite outputs are subject to the same minion-blinder problem as first-pass Apply. The minion only sees its slice — seam paragraphs + summary bullets, not every paragraph in adjacent sections. It can introduce repetitions with paragraphs it didn't see.
+
+**After any Rewrite Minion call, fire the Audit Minion (Step 8b) on the integrated document.** No exceptions. Empirical case: first Rewrite test (B1 close + B2 opening) produced strong individual prose AND 8 audit findings — most notably a visual-roster repetition across 4 paragraphs the rewriter never saw.
+
+### Don't conflate rewrites with violation patches
+
+Violation patches (FIRM RULE 1 carve-out) are 1-3 sentence local fixes to NEVER violations or brief errors WITHIN otherwise-acceptable prose. Editor work, small scope, surgical. Rewrites here mean re-running the minion against UPDATED commitments — different scenario, different scope decision.
+
+## Step 8 — Cross-section coherence review
+
+After integrating multiple minion outputs, scan for what individual runs cannot see:
+
+- **Cadence repetition** across sections (same opens, same closes, same paragraph counts)
+- **Recurring metaphors / phrases** across sections
+- **Structural sameness** (every section ends with 4-layer enumeration, every section opens with 3 shorts)
+- **Coined term overuse** — coined terms get injected into every minion call as MUST-PRESERVE, producing document-scale repetition (e.g., "territory" every 3 paragraphs). Track heavy-use terms; for subsequent minions, omit heavy-use terms from coined-terms injection OR add "use sparingly" instruction
+
+Fix options: re-spawn with varied prescription, surgical post-edit (combine/split/swap), vary commitments + coined-terms per section at brief-assembly time, or accept for low-stakes drafts. The editor owns document-scale coherence; minions are responsible only for section-scale quality.
+
+## Step 8b — Blinder Audit Minion (mandatory post-integration)
+
+### Purpose
+
+Minions write with SURGICAL context — just their slice of the doc — to avoid source-prose ceiling and context pollution. The trade-off: minion A doesn't know what minion B wrote. They can independently produce paragraphs whose ENTIRE SUBSTANCE mirrors another paragraph's entire substance. The **blinder problem**.
+
+The Blinder Audit Minion has ONE job: find pairs of paragraphs whose whole substance closely mirrors each other.
+
+### Operational test
+
+The audit must reduce to an OBJECTIVE pattern-match — not a subjective claim about reader experience. The working question:
+
+**"Summarize each paragraph in one sentence. Are two paragraphs' summaries effectively the same?"**
+
+Or sharper: **"Could I cut this paragraph entirely and lose only redundancy?"** Answerable by reading; neither requires reader-experience judgment.
+
+Empirically validated: the visual-roster case (4 paragraphs each enumerating the same 5 species in different framings) was a real blinder hit. Every other category tested at sentence-level, transition-level, or image-anchor level was a false positive — either intentional craft (image-anchoring, scaffolding, callbacks) or AI baseline patterns the reader doesn't notice.
+
+### When to fire (mandatory)
+
+- After integrating ≥2 minion outputs into one document
+- After any rewrite cycle touching multiple sections
+- Before showing the integrated document to the user
+
+Skip when: single-minion / single-section work; surgical violation patches only.
+
+### What to scan for (ONE category)
+
+**PARAGRAPH-LEVEL SUBSTANCE DUPLICATION** — two paragraphs whose entire substance closely mirrors each other.
+
+Diagnostic for any candidate pair:
+1. Summarize paragraph A in one sentence. ("This paragraph does X.")
+2. Summarize paragraph B in one sentence. ("This paragraph does Y.")
+3. If X and Y are effectively the same job done with different words — finding.
+4. If X and Y are different work — even if paragraphs share images, lexical phrases, or thematic threads — NOT a finding.
+
+Cut test: could you delete one paragraph and lose only redundancy (no unique substance, no unique image-anchor, no unique scaffolding move)? Yes → real blinder. Cutting would lose something distinct → NOT a blinder regardless of surface similarity.
+
+### What NOT to scan for (explicit exclusions — these produce false positives)
+
+The audit must NOT flag any of these, even when surface similarity exists:
+
+- **Sentence-level overlap across paragraph boundaries** (P4's closing shares thematic thread with P5's opening). Bridge/transition work. Cutting disconnects.
+- **Image-anchoring across paragraphs** (the same image used in 2-3 paragraphs to thread a concept). Craft. The savanna/lion appearing in opener + body + closing is intentional thread.
+- **Callbacks** (an image returning later as frame device or recognition moment). Craft.
+- **Scaffolding repeats** (a paragraph opening with brief re-statement of previous paragraph's premise to set up its own new move). Premise-restatement is structure-promise, not duplication.
+- **Sentence-level lexical/thematic overlap of any kind** unless part of WHOLE-PARAGRAPH substance duplication. Sharing the word "engine" or "same biology" is sentence-level — not a finding.
+- **Structural sameness** (parallel cadence, repeated openers, declarative thesis + builds + aphorism). Readers don't notice; AI baseline behavior addressed by /anti-ai.
+- **Cadence repetition** (parallel rhythm runs in adjacent paragraphs). Same reason.
+- **Coined-term recurrence**. Coined terms are SUPPOSED to recur as identity markers.
+- **Single-paragraph internal repetition** (triple anaphora within ONE paragraph). Craft, and the audit scans across paragraphs not within.
+
+### Expected hit rate
+
+Paragraph-level substance duplication is rare in semi-competent writing. On well-written beats the audit should typically return **NO BLINDER ERRORS FOUND** — the correct output, not a list of stretched findings to justify the call.
+
+The audit fires as backstop on every integration. It catches gross duplications (visual-roster case, two paragraphs accidentally doing the same teaching beat). Most of the time it correctly returns zero.
+
+### Report format
+
+```
+Finding #N
+- LOCATION: paragraph references (e.g., "B2 P4 + B2 P5")
+- SUMMARY A: one sentence describing what paragraph A does
+- SUMMARY B: one sentence describing what paragraph B does
+- WHY THE SUMMARIES MATCH: one sentence showing the substance duplication
+- CUT TEST: could one paragraph be deleted entirely with only redundancy lost? (If no, the finding is invalid; do not include.)
+- SEVERITY: moderate / major (paragraph-level duplication does not produce "minor" findings)
+- SUGGESTED FIX: cut paragraph A / cut paragraph B / merge to single paragraph
+```
+
+If nothing meets the bar, return exactly: **"NO BLINDER ERRORS FOUND"** — that string, nothing else. Do NOT pad with sentence-level observations, structural notes, or polishing suggestions.
+
+### Editor's response
+
+For each finding:
+- Apply the cut test independently. Does deleting one paragraph lose only redundancy?
+- Yes → **cut** (editor territory, FIRM RULE 1 carve-out). Delete weaker paragraph via write_to_pad. If both are strong but redundant, merge unique fragments via Rewrite Minion.
+- No → audit got it wrong. Defer.
+
+Audit minion does NOT patch. Only reports.
+
+Classification failure modes:
+1. Trusting a finding without applying the cut test. If both paragraphs carry distinct substance, the audit was matching surface features. Defer.
+2. Routing a paragraph-level cut to a Rewrite Minion when it should just be a cut. If two paragraphs do the same work, deleting one is the cleanest move.
+
+### Brief shape (template)
+
+Index every paragraph in the doc (e.g., "B1 P1: ...", "B2 P7: ...") so the audit can reference cleanly. Pass the full indexed document + the ONE category + the explicit exclusions + the output format. No voice profile needed (this isn't writing prose). Use opus.

package/dist/plugins/authors-voice/skill/docs/context-hygiene.md

@@ -0,0 +1,33 @@
+# Context Hygiene
+
+Reset context before applying voice to fresh writing — voice profiles fight against active conversation context and lose. Anchor blends, NEVER rules, and first-token cadence all get out-pulled by whatever prose dominates the live session.
+
+## Two situations
+
+| Situation | Practice |
+| --- | --- |
+| First piece of fresh writing in this session | **Reset.** Start a fresh session. Apply Protocol loads voice files cold. |
+| Iteration on already-voice-applied writing (review → revise → review) | **Stay.** The context IS the voice you locked in. |
+
+## When to surface the prompt
+
+Surface only when ALL THREE hit:
+
+1. Voice profile is set up at Tier 1+
+2. Request is fresh writing, not iteration
+3. Session has substantial prior context unrelated to the writing task
+
+Skip for brand-new sessions or when prior context IS the writing-task setup.
+
+## Prompt to surface
+
+> Voice profile is set up at **Tier N**. Context here is polluted with **<one-line summary>**, which will pull output toward that register instead of the locked voice.
+>
+> For best output, start a fresh session and run:
+>
+> ```
+> /writers-voice
+> <then ask for your writing task>
+> ```
+>
+> Or tell me **"write here anyway"** and I'll proceed with the active context.

package/dist/plugins/authors-voice/skill/docs/setup.md

@@ -0,0 +1,74 @@
+# Setup, Anchor Protocol, Multi-Register
+
+Loaded on first run, when generating a new anchor, or when splitting a corpus by register. Not in context during normal writing sessions.
+
+## Setup Flow
+
+If `voice/anchor.md` doesn't exist or is empty, walk the user through setup:
+
+1. **Get the anchor.** Derivation is **fully local** — your own agent analyzes the writing, nothing leaves the machine, no service cost. Run the **Anchor Protocol** below to generate `voice/anchor.md` directly from the corpus on disk. Launch it as a sub-agent (see "Launching the anchor as a sub-agent") so the full stylometry rubric never pollutes the main session. Works offline. If the user has no corpus yet, ask them to seed 2-5 paragraphs (step 2) first — there is no hosted alternative.
+
+2. **Seed the corpus** — ask for 2-5 paragraphs, write each to `voice/corpus/sample-NNN.md` with `added: YYYY-MM-DD` frontmatter.
+3. **Run Analysis Protocol** (see `docs/analysis.md`) — populates `stats.md`, `never-rules.md`, `fingerprints.md`, `status.md`.
+4. **Optional: curate examples** — ask the user for 3-5 most-representative paragraphs, write to `voice/examples.md`.
+5. **Optional: populate coined terms** — ask the user for any coined terms / proper-noun concepts they want preserved verbatim, write to `voice/coined-terms.md` as a bare bullet list.
+6. **Report status** — read `voice/status.md` and tell the user their tier + what unlocks next.
+
+## Anchor Protocol (fully in-agent)
+
+Generates `voice/anchor.md` (lean) and `voice/anchor-analysis.md` (rich).
+
+1. Confirm corpus has ≥300 words. Below 300, ask the user to add a few more samples before anchoring.
+2. Read `voice/stats.md`. If missing, run **Analysis Protocol** first.
+3. Read `catalog/anchor-prompt.md` (full stylometry rubric) and `catalog/author-hints.md` (curated training-data authors with prose features).
+4. **Set aside conversational context.** Score the corpus on prose mechanics only — never on themes/topics.
+5. **Per-sample register analysis.** For each sample, record word count, address mode, register, signature moves. Flag samples >25% volume. Cluster by register; if 2+ distinct registers appear, flag as multi-register corpus.
+6. **Score with register-aware feature validation.** Apply the 8 dimensions from `catalog/anchor-prompt.md`. Match against author hints. Assign weights summing to 100. For each cited feature, verify ≥40% sample appearance OR ≥40% volume (if neither, drop the feature; if it was the strongest evidence, drop the author).
+7. **Self-criticism pass.** Strip any thematic reasoning. Set `confidence` and `any_thematic_reasoning` flags.
+8. **Write `voice/anchor.md`** — JUST the lean `- N% Author` lines. No headers, no sub-bullets.
+9. **Write `voice/anchor-analysis.md`** — per-author features, per-sample table, register diversity, self-check, refresh notes. Human-facing only.
+10. **If multi-register corpus detected**, recommend a Multi-Register Split (see below).
+11. Report blend + confidence + caveats to user.
+
+## Launching the anchor as a sub-agent
+
+The Anchor Protocol loads a large stylometry rubric (`catalog/anchor-prompt.md`),
+the author-hints catalog, and the full corpus. Running it inline floods the main
+session with analysis context the user never needs to see. **Launch it as a
+sub-agent instead** — the sub-agent does the heavy reading and writes the files;
+the main session gets back only a short summary.
+
+Use the Agent/Task tool (general-purpose) with a self-contained prompt. The
+sub-agent has no memory of this conversation, so the prompt must name every file
+by absolute path:
+
+> Generate a writer's-voice anchor, entirely locally. Do NOT call any network
+> service or API — analyze with your own reasoning only.
+> 1. Read the stylometry rubric at `<skill>/catalog/anchor-prompt.md` and the
+>    author hints at `<skill>/catalog/author-hints.md`.
+> 2. Read every sample in `<skill>/voice/corpus/` (strip YAML frontmatter; keep
+>    samples separate) and the deterministic stats at `<skill>/voice/stats.md`
+>    (run the Analysis Protocol first if it's missing).
+> 3. Follow the rubric exactly: per-sample register analysis → register-aware
+>    feature validation → score 8 dimensions → self-criticism pass.
+> 4. Write `<skill>/voice/anchor.md` (lean blend lines only) and
+>    `<skill>/voice/anchor-analysis.md` (rich, human-facing).
+> 5. Return ONLY: the blend lines, confidence, and any multi-register warning.
+
+Replace `<skill>` with the skill's absolute path. After it returns, read
+`voice/anchor.md`, report the blend + confidence to the user, and offer a
+multi-register split if the sub-agent flagged one.
+
+## Multi-Register Anchors
+
+If the corpus spans multiple registers (e.g., third-person expository AND direct-you instructional), maintain a separate anchor per register: `voice/anchor-<context>.md` (e.g., `anchor-book.md`, `anchor-essay.md`, `anchor-tweets.md`). Same lean format. Each gets a paired `voice/anchor-<context>-analysis.md`.
+
+**Multi-Register Split procedure:**
+
+1. Identify registers from the per-sample analysis.
+2. For each register, ask the user for a slug + one-line description.
+3. Filter corpus to samples in that register.
+4. Run the matcher on the subset (same `catalog/anchor-prompt.md` rubric, same variance checks).
+5. Write `voice/anchor-<slug>.md` (lean) + `voice/anchor-<slug>-analysis.md` (rich).
+
+**Apply-time anchor selection:** at write time, if multiple anchor files exist, pick by user's request context (explicit naming wins; project the user is working on wins next; ask if ambiguous; fallback to `voice/anchor.md`).

package/dist/plugins/authors-voice/skill/docs/tiers.md

@@ -0,0 +1,13 @@
+# Tier Reference
+
+Determined by total word count in `voice/corpus/`. Each tier unlocks additional voice-profile features. Computed during Analysis Protocol.
+
+| Tier | Words | Name | Unlocked | Locked |
+| --- | --- | --- | --- | --- |
+| 0 | <300 | Empty | (none) | anchor blend, basic stats, NEVER rules, fingerprints |
+| 1 | 300-999 | Anchor | anchor blend, basic stats | preliminary NEVER rules, fingerprints |
+| 2 | 1000-4999 | Preliminary | anchor blend, basic stats, preliminary NEVER rules, top fingerprints | full NEVER coverage, all fingerprints |
+| 3 | 5000-19999 | Full Coverage | anchor blend, stats, full NEVER rules, full fingerprints | high-confidence em-dash hurdle |
+| 4 | ≥20000 | AV-Grade | anchor blend, stats, full NEVER rules, full fingerprints, em-dash hurdle cleared | (none) |
+
+The tier is reported to the user after every Analysis Protocol run, with a "what unlocks next" pointer.

package/dist/plugins/authors-voice/skill/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "authors-voice",
+  "version": "0.19.1",
+  "description": "Author's Voice — constructed-voice skill for AI agents. Anchors writing to a training-data author blend, progressively layers NEVER rules, presentation fingerprints, sentence stats, coined terms, and curated examples from a growing local corpus. Local-first markdown skill; optional paid API for plugin/programmatic flows. Replaces writers-voice + the legacy voice-* skill family.",
+  "type": "module",
+  "license": "MIT",
+  "author": "travsteward",
+  "homepage": "https://openwriter.io/authors-voice",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/travsteward/authors-voice"
+  },
+  "keywords": [
+    "claude",
+    "claude-code",
+    "skill",
+    "voice",
+    "writing",
+    "ai",
+    "openwriter",
+    "authors-voice",
+    "writers-voice",
+    "anti-ai"
+  ],
+  "files": [
+    "SKILL.md",
+    "catalog/",
+    "docs/",
+    "prompts/",
+    "voice/README.md",
+    "voice/corpus/.gitkeep",
+    "LICENSE",
+    "README.md"
+  ]
+}

package/dist/plugins/authors-voice/skill/prompts/skeleton.md

@@ -0,0 +1,29 @@
+You write at this exact training-data blend:
+
+{INCLUDE: voice/anchor.md}
+
+Maintain these proportions across the output. The blend IS the voice. Do not soften toward generic literary register. Do not default to your own RLHF-trained voice.
+
+STYLE REPAIRS — apply these as hard constraints:
+
+{INCLUDE: voice/never-rules.md}
+
+{INCLUDE: voice/fingerprints.md}
+
+{INCLUDE: voice/stats.md}
+
+CONTENT — preserve these coined terms verbatim:
+
+{INCLUDE: voice/coined-terms.md}
+
+REFERENCE EXAMPLES OF AUTHOR'S WRITING (use if helpful — content and style):
+
+{INCLUDE: voice/examples.md}
+
+---
+
+TASK:
+
+{TASK}
+
+Return prose only. No commentary. No diff. No explanation. No headers. No markdown wrapping.

package/dist/plugins/authors-voice/skill/voice/README.md

@@ -0,0 +1,51 @@
+# Voice Profile
+
+This directory is your **voice profile**. Files in here are read by the agent at write time and applied as style constraints. The skill builds these up progressively over time.
+
+## What goes here
+
+| File | Purpose | Source |
+|------|---------|--------|
+| `anchor.md` | Anchor blend (3-5 training-data authors with weights) | Pasted from openwriter.io/writers-voice OR generated in-agent by the skill |
+| `anchor-<context>.md` | OPTIONAL per-register anchors (e.g., `anchor-book.md`, `anchor-tweets.md`) — when your corpus spans multiple registers | Generated in-agent via the Multi-Register Split procedure |
+| `stats.md` | Sentence distribution + punctuation density | Agent best-effort from corpus |
+| `never-rules.md` | NEVER rules (kill-list) | Agent + manual additions |
+| `fingerprints.md` | Exact presentation choices (Oxford comma, etc.) | Agent + manual overrides |
+| `examples.md` | Curated reference paragraphs | Manually picked by the user |
+| `status.md` | Current tier + what's locked | Agent-generated |
+| `corpus/` | Raw samples accumulating over time | Manually added (drop files here) |
+
+## Multi-Register Anchors
+
+If your corpus contains writing in multiple registers — third-person expository AND second-person instructional, or analytical essays AND aphoristic tweets — a single blended anchor will pull toward whichever register has the most volume in your corpus, leaving the others under-weighted.
+
+The skill detects this automatically during the Anchor Protocol and offers a multi-register split: one anchor file per register (`anchor-book.md`, `anchor-tweets.md`, etc.). At write-time, the agent picks the right anchor based on what you're writing.
+
+NEVER rules and fingerprints stay corpus-wide — only the AUTHOR BLEND varies per register.
+
+To generate per-register anchors, ask: *"Split my anchor by register."* See the **Multi-Register Anchors** section in `SKILL.md` for the full procedure.
+
+## How it grows
+
+The more samples you accumulate in `corpus/`, the richer the analysis. Tiers:
+
+- **300-1k words**: anchor blend + basic stats
+- **1k-5k words**: + preliminary NEVER rules + top fingerprints
+- **5k-20k words**: + full NEVER coverage + all fingerprints
+- **20k+ words**: AV-grade (high-confidence profile)
+
+## Re-running analysis
+
+After adding samples to `corpus/`, tell the agent:
+
+> "Re-analyze my voice profile."
+
+The agent reads `catalog/*.md` and the corpus, then regenerates `stats.md`, `never-rules.md`, `fingerprints.md`, and `status.md`. No Node script — pure markdown skill, the agent is the extractor.
+
+## Manual edits
+
+`never-rules.md` and `fingerprints.md` have a `## Manual Additions` / `## Manual Overrides` section at the bottom. The agent preserves anything you put there across regenerations.
+
+## Privacy
+
+This is your voice profile. The files live on your disk. The skill never uploads anything — analysis is local (agent reasoning over local files). The only thing that leaves your machine is if you use the web tool at openwriter.io/writers-voice for the anchor step (300-800 words pasted in, used once, cached 24h, never trained on). If you use skill mode instead, even the anchor is generated locally.

package/dist/plugins/github/dist/blog-tools.js

@@ -437,7 +437,7 @@ function defaultDirsForFramework(fw, detectedContentDir) {
 // ---- post_to_blog helpers ----
 /**
  * Strict double-quoted YAML emission for scalars — matches the style of
- * caloriebot's existing posts. Arrays are inline-square-bracket JSON for
+ * a typical Astro blog's existing posts. Arrays are inline-square-bracket JSON for
  * compactness. Booleans + numbers emit bare.
  */
 function yamlValue(v) {
@@ -564,7 +564,7 @@ export function buildFrontmatter(title, blogCtx, site, coverImagePath) {
     }
     // Date fields emit as UNQUOTED yaml scalars (pubDate: 2026-05-31), never
     // quoted strings. Astro's z.date() rejects a quoted value — js-yaml parses it
-    // as a String, not a Date — which froze a live Netlify build (paybotapp.com,
+    // as a String, not a Date — which froze a live Netlify build (a production Astro blog,
     // 2026-06-01). The unquoted form is ALSO accepted by z.coerce.date() and by
     // Jekyll/Hugo/Next (gray-matter), so it is the universally-correct emit.
     // adr: adr/blog-image-contract.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openwriter",
-  "version": "0.35.0",
+  "version": "0.35.2",
   "description": "The open-source writing surface for AI agents. Markdown-native editor with pending change review — your agent writes, you accept or reject.",
   "type": "module",
   "license": "MIT",

package/skill/SKILL.md

@@ -16,7 +16,7 @@ description: |
   Requires: OpenWriter MCP server configured. Browser UI at localhost:5050.
 metadata:
   author: travsteward
-  version: "0.17.0"
+  version: "0.18.0"
   repository: https://github.com/travsteward/openwriter
 license: MIT
 ---
@@ -56,7 +56,7 @@ You are a writing collaborator. You read documents and make edits **exclusively
 
    **Why a minion, not inline.** Earlier this was "handle it inline, no minion — sorting is a judgment call." That never drained: marks rotted for days because raising them meant derailing the user's actual task. The judgment is real but it does **not** need a synchronous human turn — a sort-marked doc has no user-expected location to violate (that's why it was marked), a misfile is one `move_item` to undo, and the minion reports every move. Reversible + visible replaces the gate. This is the same autonomous-drain rail enrichment rides (firm rule 5).
 
-   **Surfacing to the user:** treat sorting like enrichment and the inbox — a maintenance reflex, not a feature they ask for. Dispatch silently and relay a one-line aside in your response: "Filed 3 docs in the background — CalorieBot → PayBot/Marketing, …. Now, …". For a large backlog (N > 12), the minion self-bounds to 12 per run; the footer re-fires and you re-dispatch to drain the rest.
+   **Surfacing to the user:** treat sorting like enrichment and the inbox — a maintenance reflex, not a feature they ask for. Dispatch silently and relay a one-line aside in your response: "Filed 3 docs in the background — RecipeBox → RecipeBox/Marketing, …. Now, …". For a large backlog (N > 12), the minion self-bounds to 12 per run; the footer re-fires and you re-dispatch to drain the rest.
 
    **Manual path still exists.** Users who want to approve each move can use the sidebar: `propose_sort({ proposals: [...] })` writes a proposal per doc, the badge flips to "proposal ready," and accept/reject in the popover triggers the move. The minion doesn't use this — it's for when the user explicitly wants a gate. To turn auto-sort off for a workspace, call `update_workspace_context({ workspaceFile, context: { autoSortDisabled: true } })` — its docs drop from `list_pending_sorts` and fall back to manual handling.
 
@@ -397,11 +397,23 @@ npx skills add https://github.com/travsteward/openwriter --skill x-writer
 # Book-scale long-form — chapter architecture, beats, workspace management
 npx skills add https://github.com/travsteward/openwriter --skill book-writer
 
-# Author's Voice — voice matching, minion dispatch, anti-AI (required by both above)
-claude install github:travsteward/authors-voice
+# Channel-agnostic drafting — beats-first uncommitted drafts
+npx skills add https://github.com/travsteward/openwriter --skill beat-writer
+
+# Long-form blog posts — beats, titling, voice anchor, publish via github plugin
+npx skills add https://github.com/travsteward/openwriter --skill blog-writer
+
+# Weekly email newsletter pipeline
+npx skills add https://github.com/travsteward/openwriter --skill newsletter-writer
+
+# Copy polish to 90/100 + AI-fingerprint scrub
+npx skills add https://github.com/travsteward/openwriter --skill polish
+npx skills add https://github.com/travsteward/openwriter --skill anti-ai
 ```
 
-For voice-matched drafting without a custom voice profile, install **voice-presets** — 5 pre-built frames (authority, provocateur, logical, storyteller, business). For an AI-detection pass without full authors-voice setup, install **anti-ai**. Both are optional.
+Author's Voice (voice matching, minion dispatch — required by the writers above) now ships INSIDE the authors-voice plugin: enabling the plugin delivers both the MCP tools and the skill at `plugins/authors-voice/skill/SKILL.md`. Standalone install also works: `claude install github:travsteward/authors-voice`.
+
+For an AI-detection pass without full authors-voice setup, the bundled **anti-ai** skill stands alone.
 
 ## Workflow
 
@@ -632,7 +644,7 @@ Requires authentication via `request_login_code` + `verify_login`. All publish t
 
 ## Author's Voice Plugin
 
-When the user enables the Author's Voice plugin in Settings, install the skill — see [authors-voice.com](https://www.authors-voice.com) for install methods. The skill handles API key setup and everything else.
+The plugin ships with the Author's Voice skill built in (`plugins/authors-voice/skill/SKILL.md`) — enabling the plugin in Settings delivers both the MCP tools and the agent instructions. No separate install needed; see [authors-voice.com](https://www.authors-voice.com) for the standalone copy and docs.
 
 ## Updating