vantage-md 0.8.1 → 0.9.1

package/CHANGELOG.md

@@ -6,6 +6,113 @@ 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.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
+
+**A planning page filtered to one piece of work.** The planning page has a
+**Filter** box at its top, there as soon as the page opens, and the page
+narrows as you type. A word, such as `generator`, finds the questions whose id,
+title, leaning or path holds it, ignoring case, and the documents whose path,
+stage or `next` does. `path:` finds its text anywhere in a path, as GitHub's
+code search does, with `*` and `**` as wildcards, and a leading `/` ties it to
+the start of the path. `is:open` keeps only open questions, as in
+`path:/docs/design/search.md is:open`, and a `-` before a term leaves out what
+it matches. The page keeps its order, a notice says what the filter hides, and
+a filter that keeps nothing says *Nothing matches* where the sections would be,
+and why. See
+[Filtering the page](userguide/guides/planning.md#filtering-the-page).
+
+Press `/` to reach the box. Paste a link to a planning page into it, as a whole
+address or as the line `vantage-check index --filter` prints, and the link's
+filter, and its roadmap if it names one, apply at once to the project on
+screen, whatever address the link was made for. The page's address follows the
+box without adding to your history. **Copy answers** and
+**Copy agent request** cover only what the filter keeps, and the agent request
+names the filter on a `Filter:` line.
+
+A planning document that holds a question now ends its Referenced by line with
+*its questions on the planning page*, a link to the planning page filtered to
+that document, unless its stage has the
+[`done` role](userguide/guides/planning.md#stage-roles). Such a document that
+nothing links to gets a line holding only that link where it had none: one with
+no open question, or any in a repository where no roadmap routes. See
+[Referenced by](userguide/guides/planning.md#referenced-by).
+
+**`vantage-check index --filter`** takes the same text, prints only what it
+keeps, and prints a `Planning page:` line for your agent to hand you.
+`vantage-check style-guide` now tells agents to hand you that line when they
+need your rulings. The checker cannot know the address you open Vantage at, so
+the link starts at `/.vantage/planning`: press `/` on your planning page and
+paste the line, or put your address in front. In daemon mode, where the link
+names no project, the planning page with no project named, or one not found,
+now lists a link to each project's planning page, keeping any filter. Run in a
+linked worktree, `--filter` adds a line under the link saying that the page
+shows the checkout your Vantage serves, which may not hold the documents as
+they are in the worktree. If your `.vantage.toml` sets a `target` before 0.9,
+another line says that an older Vantage shows every entry. Under a `target`
+before 0.8, it says first that a Vantage that old has no planning page. With
+`--format json`, the filtered sections are under a new `filter` key. Every
+other key, `sections` included, is what it is without the flag, and the format
+version stays 2.
+
+`--filter` exits `2` on a filter it cannot read, such as one with an unclosed
+quote, and on a `path:` or `-path:` term that matches no path. A word that
+matches nothing is an empty answer and exits `0`. `vantage-check` 0.8.0 and
+0.8.1 exit `2` with `unknown option for index: --filter`: run
+`uvx vantage-check@latest`. Vantage 0.8.0 and 0.8.1 ignore the filter without
+saying so: they show the whole planning page, or, in daemon mode, ask you to
+choose a project. A later release may keep other entries for the same filter
+text, so have your agent rerun `--filter` rather than keep an old link. See
+[Handing the human a filtered planning page](userguide/guides/vantage-check.md#handing-the-human-a-filtered-planning-page).
+
+### Fixed
+
+- In daemon mode, `g p` and the sidebar's planning entry opened the wrong page
+  for a project whose name holds `#` or `?`.
+- On the planning page, the roadmap picker at the top of the contents column
+  drew its focus ring cut off at the left edge.
+
 ## [0.8.1] - 2026-10-02
 
 If your `.vantage.toml` sets a `target` before 0.8, such as `target = "0.7"`,

package/dist/index.cjs

@@ -2773,6 +2773,7 @@ BUILT = "built"
 SUPERSEDED = "done"
 \`\`\`
 - **Each stage word maps to one of four roles**, which is what the word means to Vantage: \`open\` is still being decided, \`ready\` is decided and not built, \`built\` is built, and \`done\` is no longer a live proposal, so its questions leave every list of what needs a ruling. \`vantage-check index\` prints those lists.
+- **To ask a human for the rulings a piece of work needs, hand them a filtered planning page.** In the checkout their Vantage serves, name the work's documents from the root with a leading \`/\`: the design, its \`-plan.md\` if one exists, and what its \`depends-on\` names. Run \`vantage-check index --filter 'path:/<design> path:/<plan> is:open'\`, and give the human the \`Planning page:\` line: they press \`/\` on their planning page and paste it, or type the filter text into its Filter box. Once you have applied their answers, the same command lists what is still open.
 - **Never change \`target\`.** A \`target = "X.Y"\` line at the top of \`.vantage.toml\` names the oldest Vantage release the repository's readers use, and only a human edits it. A \`vantage-check\` older than the target refuses to run and names the release it needs: run that release, and leave the target as it is.
 
 ### Mermaid diagrams