vantage-md 0.9.0 → 0.9.2

package/CHANGELOG.md

@@ -6,6 +6,56 @@ are summarized one section per minor line; the commit log has the rest.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.9.2] - 2026-10-08
+
+### Fixed
+
+- `vantage-check` no longer asks you to link a file that git ignores. If a
+  committed document names a private, gitignored file — a local config file
+  that exists on your machine and nowhere else — the checker used to flag that
+  name on your machine and let it pass in a clean checkout. It now leaves the
+  mention alone. A link you wrote to that file is still checked.
+
+## [0.9.1] - 2026-10-06
+
+### Changed
+
+**A planning link from `vantage-check` opens its own project when one Vantage
+serves several.** The `Planning page:` link that `vantage-check index --filter`
+prints now ends with `&space=`, an id naming the checkout it ran in, and so
+does `filter.link` under `--format json`. Put your Vantage's address in front
+of the link and open it. In daemon mode, the page asks Vantage which project
+holds that id and opens that project's planning page with the filter, with no
+list of projects on the way. In 0.9.0 it listed every project's planning page
+for you to pick from. A link made in a checkout your Vantage does not serve
+says so, and in daemon mode only then shows that list. Pasting the line into
+the Filter box works as before. See
+[Filtered links](userguide/guides/planning.md#filtered-links).
+
+**`index --filter` now writes `.vantage/space`.** The first run that prints a
+link makes the file at the project root, holding the id, and later runs reuse
+it. The checker keeps the id out of git, so that every clone gets its own.
+When it makes `.vantage` itself, it also writes a `.vantage/.gitignore` that
+ignores the whole directory. A `.vantage` that is already there with no
+`.gitignore`, as the review inbox can leave one, gets one that ignores only the
+id. A `.vantage/.gitignore` you already have is left alone, so make sure it
+ignores `space`. A linked worktree gets an id of its own. A checkout copied
+whole, `.vantage` included, shares the original's id, so a link from either
+opens neither and the page lists both: remove `.vantage/space` in the copy. See
+[What `--filter` writes](userguide/guides/vantage-check.md#what---filter-writes).
+
+The checker and the viewer both need 0.9.1. Vantage 0.9.0 ignores `space=`
+and lists each project's planning page as before, and a link from
+`vantage-check` 0.9.0 has no `space=`.
+
+### Fixed
+
+- Moving between pages, such as from a document to the planning page with
+  `g p`, no longer flashes the *Disconnected from backend* banner.
+- A planning link written in a document, such as a `Planning page:` line in an
+  agent's handoff note, opened as a path inside that document's project. It now
+  opens the planning page.
+
 ## [0.9.0] - 2026-10-06
 
 ### Added

package/dist/index.cjs

@@ -2689,6 +2689,20 @@ function resolveLinks(html, options = {}) {
 * Every rule stated here should be one a checker can enforce or a renderer
 * actually cares about — if a line is neither, it does not belong.
 */
+/**
+* Shared by the style guide and every review clipboard payload. These are
+* authoring instructions, not a claim that the checker measures agent latency.
+*/
+const ANSWER_PROCESSING_GUIDE = `### Record rulings before downstream work
+
+Vantage derives planning state from saved Markdown. Pending review comments can show an answer waiting on the agent, but an agent reply does not settle the question in the document; replying first can make it need the human again.
+
+- **Record a clear ruling first**, in the checkout Vantage serves, before launching or continuing downstream work based on it. Do not wait for a larger rewrite, implementation, independent review, a full test suite, or a commit. A saved edit in another worktree does not update this interface.
+- **Finish a small, coherent document update.** Fold the ruling into the body it governs, then compact the settled question into a Decision Ledger row retaining its exact ID, decision, date, and a link to the governing section. Remove the question's directive only with that compaction; repair inbound Markdown links to its former anchor in the same update. Keep question-specific \`depends-on\` fragments when the ledger retains their IDs. Preserve the decision, not the discarded options and leaning.
+- **Keep unfinished work visible.** A decision is not evidence that it has been implemented. Update \`status\`, \`stage\`, \`next\`, and dependencies only as warranted; do not claim \`accepted\` while any question remains unanswered, including blocked ones, or use a \`done\` stage to hide work. A clarification request is not a ruling: reply without closing the question. For a partial answer, record the settled part and retain a narrower open question with its directive.
+- **Save each coherent update promptly**, rather than waiting for every document in the batch. The coordinator records rulings before handing those documents to a writer. Do not overwrite another writer's changes; if the served checkout is unavailable or the edit conflicts, report that obstacle explicitly instead of claiming the interface has updated.
+- **Then check the affected documents and deliver the comment responses.** Deliver responses for recorded rulings promptly, without waiting for downstream work or the rest of the batch. A response says what was recorded and what remains unbuilt. Do not claim the question is settled while its document is still open. Missing checker tooling does not justify postponing the saved update. Vantage cannot verify from prose alone that a ruling was incorporated correctly or enforce this ordering on an external agent.
+`;
 const STYLE_GUIDE = `## Markdown style guide (for Vantage viewer)
 
 When writing or updating markdown documents that will be viewed in Vantage, follow these conventions:
@@ -2896,6 +2910,7 @@ A question a document leaves for a human to rule on is an *Open Question*, writt
 - **Write a question as a list item.** Outside a list, a question runs from the block its directive lands on through the blocks after it, up to the next heading (for a question written as a heading, the next one of its level or higher), the next rule or the next question, so whatever prose follows it before then is read as part of it. There the directive goes above the question's title, since every viewer reads the question's marker from the block it lands on: a directive below the bold title lands on the block after it, which carries no marker, so every viewer reads the question as open. \`vantage-check\` reports that as \`vantage/question-name\`.
 - **\`oq\` is the name \`question\` replaces.** Vantage keeps reading \`<!-- vantage: oq id=OQ-9 leaning="…" -->\` as it always has, and \`vantage-check\` warns on it (\`vantage/oq-deprecated\`) with the \`question\` to write instead, keys unchanged. Vantage before 0.8 drops \`question\` whole, so a reader still on 0.7 gets no one-click answer and no anchor on a question written with it, and misreads nothing. So keep an \`oq\` on an open question unless you know every reader of the repository is on 0.8 or later. A repository whose readers are still on 0.7 says so with a \`target\` before 0.8, such as \`target = "0.7"\`: there an open question takes \`oq\`, new ones included, and \`vantage-check\` asks for \`oq\` rather than \`question\` on one. **Never put \`oq\` on a \u{1F512} or \u2705 question**: every Vantage before 0.8 offers the one-click button on every \`oq\`, whatever its marker says, and on a question with no leaning it files the literal text "Take the stated leaning." \`vantage-check\` reports that as an error (\`vantage/question-name\`).
 
+${ANSWER_PROCESSING_GUIDE}
 ### Tables, task lists, and math
 - **Tables**: Use standard markdown tables for structured comparisons and schemas.
 - **Task lists**: Use \`- [ ]\` and \`- [x]\` for actionable checklists and status tracking.
@@ -2904,6 +2919,7 @@ A question a document leaves for a human to rule on is an *Open Question*, writt
 `;
 //#endregion
 exports.ALERT_TITLES = ALERT_TITLES;
+exports.ANSWER_PROCESSING_GUIDE = ANSWER_PROCESSING_GUIDE;
 exports.COLOR_THEME_ATTRIBUTE = COLOR_THEME_ATTRIBUTE;
 exports.COLOR_THEME_SOURCE_ATTRIBUTE = COLOR_THEME_SOURCE_ATTRIBUTE;
 exports.DIRECTIVE_NAMES = DIRECTIVE_NAMES;