stego-cli 0.1.1

package/docs/conventions.md

@@ -0,0 +1,182 @@
+# Creative Writing Conventions
+
+## 1) Canonical ordering and metadata
+
+Each manuscript file lives in:
+
+`/Users/mattgold/Code/writing/projects/<project-id>/manuscript/`
+
+Naming convention (order-oriented, not chapter-oriented):
+
+- `100-opening-image.md`
+- `200-market-interruption.md`
+
+Default metadata preference (global):
+
+```yaml
+---
+status: draft
+---
+```
+
+Per-project metadata preferences can be set in `stego-project.json`:
+
+```json
+{
+  "requiredMetadata": ["status", "chapter", "pov", "timeline"]
+}
+```
+
+These keys are advisory and reported as warnings when missing; they do not block validate/build/export.
+Manuscript files can omit metadata blocks.
+
+Optional metadata:
+
+- `title`: optional override for display heading; default is derived from filename
+- grouping keys/titles defined by your project's `compileStructure.levels` (for example `part`, `part_title`, `chapter`, `chapter_title`)
+- category arrays defined by your project's `spineCategories` config (example: `cast`, `places`, `incidents`, `ordinances`)
+
+Rules:
+
+- Filename must start with a numeric prefix followed by `-` or `_` (example: `100-scene.md`).
+- Use three-digit prefixes and leave gaps (`100`, `200`, `300`) to make reordering easy.
+- `status` must be one of: `draft`, `revise`, `line-edit`, `proof`, `final`.
+- Build sorts by filename prefix order.
+- Group headings/page breaks are driven by `compileStructure.levels` key changes across ordered files.
+- Canon references belong in metadata arrays defined by project configuration.
+- Do not place canon IDs directly in prose.
+
+Compile structure rules:
+
+- `compileStructure.levels` is optional; when omitted, build emits entry sections only (no structural group headings).
+- Each level defines: `key`, `label`, optional `titleKey`, optional `injectHeading`, optional `headingTemplate`, optional `pageBreak` (`none` or `between-groups`).
+- Missing group key/title values inherit from the previous manuscript file, so only boundary files need explicit group metadata.
+
+## 2) Project-defined spine categories
+
+Spine categories are configured per project in `stego-project.json`.
+
+Example:
+
+```json
+{
+  "id": "my-project",
+  "title": "My Project",
+  "spineCategories": [
+    { "key": "cast", "prefix": "CHAR", "notesFile": "characters.md" },
+    { "key": "places", "prefix": "LOC", "notesFile": "locations.md" },
+    { "key": "incidents", "prefix": "EVENT", "notesFile": "timeline.md" },
+    { "key": "ordinances", "prefix": "STATUTE", "notesFile": "ordinances.md" }
+  ]
+}
+```
+
+Category rules:
+
+- `key`: lowercase metadata field name used in manuscript files
+- `prefix`: uppercase ID prefix used in references (example: `STATUTE`)
+- `notesFile`: markdown filename resolved in `spine/` containing canonical entries
+- `spineCategories` may be omitted or empty for projects that do not need continuity entity tracking
+
+## 3) Spine governance
+
+Every project keeps canonical story facts in:
+
+`/Users/mattgold/Code/writing/projects/<project-id>/spine/`
+
+Required spine files are determined by `spineCategories[*].notesFile`.
+
+Governance rule:
+
+- If manuscript facts change, update the relevant spine file in the same branch before merge.
+- Canon IDs are referenced from manuscript metadata, not inline prose.
+
+## 4) Editorial states
+
+- `draft`: drafting only, minimal enforcement.
+- `revise`: structural edits and continuity corrections.
+- `line-edit`: sentence-level edits, grammar and spelling focus.
+- `proof`: publication polish with strict link/lint/spell checks.
+- `final`: release candidate; all manuscript files should be `final`.
+
+## 5) Quality gates
+
+Blocking checks:
+
+- malformed or missing metadata
+- invalid `compileStructure` schema in `stego-project.json`
+- invalid required metadata
+- duplicate filename numeric prefixes
+- invalid category reference metadata (bad format or wrong field type)
+- inline canon IDs in prose (metadata-only policy)
+- broken local links/images (strict in `proof` and `final`)
+- stage mismatch (file status below requested stage)
+
+Advisory checks:
+
+- heading-level jumps
+- long paragraphs/sentences
+- unknown spine IDs referenced in metadata
+- optional external lint/spell tool feedback
+
+## 6) Build contract
+
+Build command compiles all manuscript files for one project into exactly one manuscript Markdown file.
+
+Contract:
+
+- Input: `manuscript/*.md`
+- Pre-step: metadata and structure validation
+- Ordering: filename numeric prefix
+- Structural headers/page breaks: inserted when configured `compileStructure.levels` keys change
+- Output: `dist/<project-id>.md`
+- Output includes generated title header, table of contents, structural sections (if configured), and per-file subsections
+- Generated files in `dist/` are never hand-edited
+
+## 7) Release outputs
+
+Current targets:
+
+- required: compiled `.md`
+- optional: `.docx` and `.pdf` via `pandoc`
+
+Design principle:
+
+- export uses a pluggable abstraction so future formats can be added without changing manuscript structure.
+
+## 8) Git conventions
+
+Branching:
+
+- Work on short-lived branches from `main`.
+
+Commit message format:
+
+- `manuscript: revise file 07 pacing`
+- `notes: update CHAR-MIRA arc`
+- `build: tighten metadata validation`
+
+Tag milestones:
+
+- `<project-id>/v0.1-draft`
+- `<project-id>/v0.2-revise`
+- `<project-id>/v1.0-final`
+
+Policy:
+
+- no force-push to `main`
+- merge only when stage checks pass for the intended stage
+- manuscript fact changes require matching spine updates
+
+## 9) Backup and resilience
+
+Use three layers:
+
+- local git history
+- remote private origin (GitHub/GitLab)
+- machine backup (Time Machine or equivalent)
+
+Recovery principle:
+
+- source of truth is `manuscript/` and `notes/`
+- `dist/` is reproducible output and may be regenerated any time

package/docs/workflow.md

@@ -0,0 +1,78 @@
+# Workflow Plan
+
+## Daily writing loop
+
+1. Pick project and target manuscript file.
+2. Open the project folder (`projects/<project-id>`).
+3. Write in VS Code in `manuscript/*.md`.
+4. Set file metadata preferred by that project's `stego-project.json` (`requiredMetadata`).
+5. Run validate/build locally.
+6. Run stage check for current milestone.
+7. Commit and push.
+
+## Commands
+
+From `/Users/mattgold/Code/writing`:
+
+```bash
+npm run list-projects
+npm run new-project -- --project <project-id> --title "<title>"
+npm run validate -- --project <project-id>
+npm run build -- --project <project-id>
+npm run check-stage -- --project <project-id> --stage <draft|revise|line-edit|proof|final>
+npm run export -- --project <project-id> --format <md|docx|pdf>
+```
+
+From a project directory (`/Users/mattgold/Code/writing/projects/<project-id>`):
+
+```bash
+npm run validate
+npm run build
+npm run check-stage -- --stage revise
+npm run export -- --format md
+```
+
+## Structural grouping model (file-first)
+
+- Keep one file per writing unit (scene, beat, section, or chapter fragment).
+- Use filename prefixes (`100-...`, `200-...`, `300-...`) for sequencing.
+- Configure `compileStructure.levels` in `stego-project.json` for grouping (for example `part` + `chapter`).
+- Build inserts headings and optional page breaks when configured grouping keys change.
+- Missing group key/title values inherit from the previous manuscript file, so boundary files carry the metadata.
+
+## Spine category model (project-defined)
+
+- Configure `spineCategories` in each project's `stego-project.json`.
+- Choose category names and ID prefixes that match your domain.
+- Keep IDs out of prose; use metadata arrays for references.
+- Keep each category's canonical entries in `spine/<notesFile>`.
+- Omit `spineCategories` if a project does not need continuity entity tracking.
+
+## Stage progression model
+
+- Start with `draft` while creating new text.
+- Move to `revise` when story structure is stable.
+- Move to `line-edit` once structure is settled.
+- Move to `proof` before sharing with readers/editors.
+- Move to `final` when preparing release snapshots.
+
+## Suggested milestones
+
+1. `v0.1-draft`: complete rough draft.
+2. `v0.2-revise`: major structural edits complete.
+3. `v0.3-line-edit`: language tightening complete.
+4. `v0.4-proof`: strict checks pass.
+5. `v1.0-final`: release candidate.
+
+## AI integration guardrails
+
+- AI suggestions should be review-first (diff/patch/report), not silent overwrite.
+- Keep human approval as required step before manuscript changes.
+- Treat AI outputs as advisory during `draft` and `revise`.
+- Allow stricter AI-assisted checks in `line-edit` and `proof` if useful.
+
+## Backup routine
+
+- Push to remote at end of each writing session.
+- Maintain machine-level backup daily.
+- Create milestone tags before major rewrites.

package/package.json

@@ -0,0 +1,50 @@
+{
+  "name": "stego-cli",
+  "version": "0.1.1",
+  "type": "module",
+  "description": "Installable CLI for the Stego writing monorepo workflow.",
+  "bin": {
+    "stego": "dist/stego-cli.js"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "files": [
+    "dist/**",
+    "docs/**",
+    "projects/**",
+    "!projects/*/dist/*.md",
+    "!projects/*/dist/exports/**",
+    ".vscode/tasks.json",
+    ".vscode/extensions.json",
+    ".gitignore",
+    ".markdownlint.json",
+    ".cspell.json",
+    "stego.config.json",
+    "README.md"
+  ],
+  "scripts": {
+    "build:cli": "tsc -p tsconfig.build.json",
+    "compile": "npm run build:cli",
+    "prepack": "npm run build:cli",
+    "pack:dry-run": "npm pack --dry-run",
+    "changeset": "changeset",
+    "release:version": "changeset version",
+    "list-projects": "node --experimental-strip-types tools/stego-cli.ts list-projects",
+    "new-project": "node --experimental-strip-types tools/stego-cli.ts new-project",
+    "validate": "node --experimental-strip-types tools/stego-cli.ts validate",
+    "build": "node --experimental-strip-types tools/stego-cli.ts build",
+    "check-stage": "node --experimental-strip-types tools/stego-cli.ts check-stage",
+    "export": "node --experimental-strip-types tools/stego-cli.ts export",
+    "test:compile-structure": "node --test tools/test/compile-structure.test.mjs",
+    "test": "npm run test:compile-structure"
+  },
+  "devDependencies": {
+    "@changesets/cli": "^2.29.8",
+    "@types/node": "^25.2.3",
+    "cspell": "^9.6.4",
+    "markdownlint-cli": "^0.47.0",
+    "pandoc": "^0.2.0",
+    "typescript": "^5.9.3"
+  }
+}

package/projects/docs-demo/README.md

@@ -0,0 +1,20 @@
+# Stego Documentation Demo
+
+A nonfiction and business-style demo project.
+
+This project intentionally keeps config minimal while documenting the full Stego feature set.
+
+- no `spineCategories` in this project's `stego-project.json`
+- no Spine continuity enforcement in this demo project
+- manuscripts include documentation of fiction and Spine capabilities
+- metadata remains lightweight (`status` plus optional chapter grouping)
+
+Use this demo when you want to show Stego as documentation workflow infrastructure while still explaining fiction workflows.
+
+Run from `/Users/mattgold/Code/stego`:
+
+```bash
+npm run validate -- --project docs-demo
+npm run build -- --project docs-demo
+npm run export -- --project docs-demo --format md
+```

package/projects/docs-demo/manuscript/100-what-stego-is.md

@@ -0,0 +1,37 @@
+---
+status: draft
+chapter: 1
+chapter_title: Overview
+---
+
+# What Stego Is
+
+Stego is a Markdown-first writing system for long-form projects.
+
+It combines source files, validation, stage gates, and export in one project structure so teams can move from draft to release without switching tools.
+
+## Core model
+
+A Stego project has four working areas:
+
+- `manuscript/`: canonical source text
+- `notes/`: planning, references, and process docs
+- `spine/`: canonical entity definitions for fiction projects
+- `dist/`: generated outputs only
+
+## What Stego standardizes
+
+- metadata in frontmatter (`status` required by default)
+- quality checks by stage (`draft` through `final`)
+- deterministic build into a single manuscript file
+- export to `md`, `docx`, `pdf`, and `epub`
+
+## Who this is for
+
+Stego is useful for both narrative and operational writing:
+
+- fiction writers and story teams
+- technical and product documentation teams
+- internal policy/process authors
+
+This demo project is documentation-first, but the next chapter also documents fiction and Spine usage.

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

@@ -0,0 +1,69 @@
+---
+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

@@ -0,0 +1,36 @@
+---
+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

@@ -0,0 +1,42 @@
+---
+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/notes/implementation-notes.md

@@ -0,0 +1,17 @@
+# Implementation Notes
+
+## Goal
+
+Show that Stego works for product docs, procedures, and internal writing systems, not only fiction.
+
+## Demo constraints
+
+- Do not use Spine identifiers in manuscript metadata.
+- Keep metadata minimal so onboarding stays simple.
+- Keep chapters independently readable.
+
+## Audience
+
+- Product and operations teams
+- Technical writers
+- Solo builders documenting process

package/projects/docs-demo/notes/style-guide.md

@@ -0,0 +1,7 @@
+# Style Guide
+
+- Write in clear operational language, not narrative prose.
+- Prefer short sections with explicit headings.
+- Keep recommendations actionable and testable.
+- Use examples that map directly to Stego commands and files.
+- Avoid tool-internal jargon when a plain term is enough.

package/projects/docs-demo/package.json

@@ -0,0 +1,10 @@
+{
+  "name": "writing-project-docs-demo",
+  "private": true,
+  "scripts": {
+    "validate": "node --experimental-strip-types ../../tools/stego-cli.ts validate",
+    "build": "node --experimental-strip-types ../../tools/stego-cli.ts build",
+    "check-stage": "node --experimental-strip-types ../../tools/stego-cli.ts check-stage",
+    "export": "node --experimental-strip-types ../../tools/stego-cli.ts export"
+  }
+}

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

@@ -0,0 +1,9 @@
+{
+  "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

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

package/projects/plague-demo/README.md

@@ -0,0 +1,19 @@
+# Under Saturn's Breath (Demo)
+
+A full-configuration demo with rich metadata, three spine categories, cross-linked spine entries, and external reference links.
+
+- four manuscript files with full metadata (`status`, `chapter`, `pov`, `timeline`, plus category arrays)
+- three spine categories: `characters`, `locations`, `sources`
+- spine category files now live in `spine/` (regular notes stay in `notes/`)
+- spine entries cross-link between files (characters reference sources they use, locations reference the characters and sources tied to them)
+- `sources` category tracks intellectual traditions rather than physical objects, with Wikipedia links to historical references
+- demonstrates the full range of stego's continuity tracking and metadata validation
+
+Run from `/Users/mattgold/Code/stego`:
+
+```bash
+npm run validate -- --project plague-demo
+npm run build -- --project plague-demo
+npm run check-stage -- --project plague-demo --stage draft
+npm run export -- --project plague-demo --format md
+```

package/projects/plague-demo/manuscript/100-the-commission.md

@@ -0,0 +1,24 @@
+---
+status: revise
+chapter: 1
+chapter_title: The Framework
+pov: Matthaeus
+timeline: '1348-09-18'
+characters:
+  - CHAR-MATTHAEUS
+  - CHAR-ETIENNE
+  - CHAR-RAOUL
+locations:
+  - LOC-COLLEGE
+sources:
+  - SRC-CONJUNCTION
+  - SRC-GALEN
+---
+
+Canon Raoul arrived before vespers with sealed instructions from men who did not sign their names. The commission was simple in expression and impossible in execution: produce an account of the pestilence that would sustain public discipline, satisfy the faculty, and be true. Raoul did not rank these requirements. Matthaeus understood that the ranking was the actual task.
+
+He accepted because refusal was not among the options and because explanation, as such, was a duty he believed in. He told Etienne to prepare two ledgers: one for accepted causes, one for observations not yet reconciled. He expected the second ledger to empty into the first as the work progressed. That was what reconciliation meant — not that everything would be easy, but that everything would eventually belong somewhere.
+
+His framework was a hierarchy. At the top, celestial disposition: the conjunction of Saturn, Jupiter, and Mars corrupting the air universally. Below that, the Galenic layer: individual complexion determining who sickened and who did not. Below that, local conditions — climate, trade, proximity. Every level consistent with the one above it. Every observation assigned a position.
+
+When Raoul left, Matthaeus unlocked a coffer beneath the desk and withdrew a loose quire copied from a prohibited tradition of astral image-magic. He consulted it only in private, not for its conclusions but for its method: how to reason from correspondences when causes were hidden. Etienne saw the motion and looked away. Between them, this silence had long been a professional courtesy.

package/projects/plague-demo/manuscript/200-at-the-wards.md

@@ -0,0 +1,38 @@
+---
+status: revise
+pov: Matthaeus
+timeline: '1348-09-21'
+characters:
+  - CHAR-MATTHAEUS
+  - CHAR-ETIENNE
+  - CHAR-AGNES
+locations:
+  - LOC-HOTELDIEU
+  - LOC-QUAY
+sources:
+  - SRC-WARD-DATA
+  - SRC-CONJUNCTION
+  - SRC-GALEN
+---
+
+At Hôtel-Dieu, prayer and treatment proceeded in one rhythm. Priests read offices while surgeons opened buboes. Women washed linen in vinegar while clerks recited names for the burial lists. Nobody in that room believed they were choosing between faith and medicine. The distinction did not apply.
+
+Matthaeus and Etienne recorded onset dates, households, trades, parish boundaries. They worked quickly because the data changed every hour. Agnes met them at the supply entrance and walked them through her own records — a set of tallies she had kept since August, organized not by humoral type or celestial sign but by street and supplier.
+
+Her map was simple. Neighborhoods tied to the grain quay sickened first. Adjacent streets followed within days. The rest of the city came after. The pattern was consistent across three months of data.
+
+At the quay she showed them torn sackcloth from a riverside storehouse and asked what his conjunction tables would have predicted for this street, this month. Matthaeus answered in the terms his system provided: commerce might distribute the material substrate, but the disposition of bodies to receive corruption remained celestial. Agnes said that might be true and still leave the wrong people dead first.
+
+He wrote her observation in the second ledger. He expected to reconcile it later. The framework had room. It had been designed to have room.
+
+<!-- stego-comments:start -->
+
+<!-- comment: CMT-0001 -->
+<!-- meta64: eyJzdGF0dXMiOiJvcGVuIiwiY3JlYXRlZF9hdCI6IjIwMjYtMDItMjFUMDM6MTk6MDUuNDg5WiIsInRpbWV6b25lIjoiQW1lcmljYS9OZXdfWW9yayIsInRpbWV6b25lX29mZnNldF9taW51dGVzIjotMzAwLCJwYXJhZ3JhcGhfaW5kZXgiOjAsImV4Y2VycHRfc3RhcnRfbGluZSI6MTgsImV4Y2VycHRfc3RhcnRfY29sIjoyMzAsImV4Y2VycHRfZW5kX2xpbmUiOjE4LCJleGNlcnB0X2VuZF9jb2wiOjIzOH0 -->
+> _Feb 21, 2026, 3:19 AM — mattgold_
+>
+> > “choosing”
+>
+> dfsf
+
+<!-- stego-comments:end -->