stego-cli 0.1.5 → 0.1.7

package/projects/docs-demo/manuscript/200-writing-workflow.md

@@ -1,69 +0,0 @@
----
-status: revise
-chapter: 1
-chapter_title: Overview
----
-
-# Fiction Workflow and Spine Features
-
-This project does not enable Spine categories, but Stego fully supports them.
-
-## How Spine works in Stego
-
-In fiction projects, `stego-project.json` can define spine categories like:
-
-- `characters` with prefix `CHAR`
-- `locations` with prefix `LOC`
-- `sources` with prefix `SRC`
-
-Each category maps to a markdown file under `spine/`.
-
-## Identifier model
-
-Spine entries use stable identifiers such as:
-
-- `CHAR-MATTHAEUS`
-- `LOC-HOTEL-DIEU`
-- `SRC-GALEN`
-
-Writers can reference these identifiers directly in manuscript metadata and prose.
-
-## Sidebar and Spine Browser behavior
-
-In the Stego VS Code extension, identifiers become interactive:
-
-- click from manuscript metadata to open Spine Browser context
-- browse categories and entries from Browser home
-- inspect entry markdown, links, and backlinks
-- track references across manuscript and notes
-
-## Why this matters for fiction
-
-Spine structure gives fiction teams a canonical layer for consistency:
-
-- one source of truth for entities
-- traceability from manuscript usage to canonical entry
-- faster continuity review during revise/proof stages
-
-
-<!-- stego-comments:start -->
-
-### CMT-0001
-<!-- meta64: eyJzdGF0dXMiOiJvcGVuIiwiYW5jaG9yIjoicGFyYWdyYXBoIiwicGFyYWdyYXBoX2luZGV4IjoxMywic2lnbmF0dXJlIjoiZm52MWE6MWE2YmJhOWEiLCJleGNlcnB0IjoiIyMgV2h5IHRoaXMgbWF0dGVycyBmb3IgZmljdGlvbiJ9 -->
-> _2026-02-20T03:46:52.817Z | mattgold_
->
-> test
-
-### CMT-0002
-<!-- meta64: eyJzdGF0dXMiOiJvcGVuIiwiYW5jaG9yIjoicGFyYWdyYXBoIiwicGFyYWdyYXBoX2luZGV4IjoxMywic2lnbmF0dXJlIjoiZm52MWE6MWE2YmJhOWEiLCJleGNlcnB0IjoiIyMgV2h5IHRoaXMgbWF0dGVycyBmb3IgZmljdGlvbiJ9 -->
-> _2026-02-20T03:47:21.646Z | mattgold_
->
-> yes yes we knoow
-
-### CMT-0003
-<!-- meta64: eyJzdGF0dXMiOiJvcGVuIiwiYW5jaG9yIjoicGFyYWdyYXBoIiwicGFyYWdyYXBoX2luZGV4IjoxMywic2lnbmF0dXJlIjoiZm52MWE6MWE2YmJhOWEiLCJleGNlcnB0IjoiIyMgV2h5IHRoaXMgbWF0dGVycyBmb3IgZmljdGlvbiJ9 -->
-> _2026-02-20T03:50:27.114Z | mattgold_
->
-> test
-
-<!-- stego-comments:end -->

package/projects/docs-demo/manuscript/300-quality-gates.md

@@ -1,36 +0,0 @@
----
-status: line-edit
-chapter: 2
-chapter_title: Quality Pipeline
----
-
-# Validation and Stage Gates
-
-Stego separates baseline validation from stage-specific enforcement.
-
-## Baseline validate
-
-`validate` checks project and manuscript integrity, including:
-
-- frontmatter parse and metadata structure
-- markdown structure and local link integrity
-- project and manuscript layout assumptions
-
-## Stage gate model
-
-`check-stage` applies stricter checks as status increases:
-
-- `draft`: structure-first, low friction
-- `revise`: continuity expectations for Spine projects
-- `line-edit`: spell-check enabled
-- `proof`: markdown lint, spell-check, strict local links
-- `final`: same strictness as proof with final-status expectations
-
-## File-scoped and project-scoped checks
-
-Stego supports both:
-
-- local file checks during active editing
-- project-wide stage checks before release
-
-In the extension UI, local checks run from manuscript status controls, while project checks run from the sidebar header.

package/projects/docs-demo/manuscript/400-build-and-export.md

@@ -1,42 +0,0 @@
----
-status: line-edit
-chapter: 2
-chapter_title: Quality Pipeline
----
-
-# Build and Export Operations
-
-Stego keeps authoring and distribution predictable.
-
-## Build behavior
-
-`build` compiles manuscript sources into one output markdown file in `dist/`.
-
-Use build output for:
-
-- full-read review passes
-- stakeholder circulation
-- archival snapshots of a known state
-
-## Export formats
-
-`export` supports:
-
-- `md`
-- `docx`
-- `pdf`
-- `epub`
-
-`docx`, `pdf`, and `epub` require `pandoc`. `pdf` also requires a PDF engine (for example `tectonic`, `xelatex`, or `pdflatex`).
-
-## Recommended release sequence
-
-1. Run file checks while drafting.
-2. Run project stage checks before release.
-3. Run build.
-4. Export the target format.
-5. Archive output from `dist/exports` as release artifacts.
-
-## Practical note for documentation teams
-
-You can document Spine features and fiction workflows in a project like this one without enabling Spine categories. That keeps docs simple while still covering the full Stego feature set.

package/projects/docs-demo/stego-project.json

@@ -1,9 +0,0 @@
-{
-  "id": "docs-demo",
-  "title": "Stego Documentation Demo",
-  "subtitle": "A business and nonfiction style project without Spine categories",
-  "author": "Matt Gold",
-  "requiredMetadata": [
-    "status"
-  ]
-}

package/projects/plague-demo/.markdownlint.json

@@ -1,4 +0,0 @@
-{
-  "default": true,
-  "MD041": false
-}