vyos-documentation.git/context7.json, branch rolling

docs: expand Context7 branch-to-version mapping rule (#2126)

2026-07-02T15:32:59+00:00

* docs: expand Context7 branch-to-version mapping rule Rule 29 in context7.json only mapped circinus (1.5.x) and sagitta (1.4.x). Expand it to the full branch-to-version table matching AGENTS.md: rolling (1.5+), circinus (1.5.x LTS), sagitta (1.4.x LTS), equuleus (1.3.x legacy), crux (1.2.x legacy). 🤖 Generated by [robots](https://vyos.io) * docs: correct rolling branch version in Context7 mapping CodeRabbit review: `rolling` was described as "1.5+", but circinus is already the 1.5 LTS line, so rolling tracks the next major (1.6+), not 1.5. Fix the rolling entry accordingly. 🤖 Generated by [robots](https://vyos.io)

docs: address review on context7 rules — show in both modes

2026-05-10T18:48:58+00:00

Two more corrections from Copilot review on #1946: Rule 2: `show` exists in both modes. Config-mode `show` displays the working config (verified: `docs/cli.md:389` wraps `show` in `{cfgcmd}`). Op-mode `show` displays running state. Previous wording listed `show` under operational mode only, which contradicted `cli.md`. Reframe to list `show` in both, scoped to "config-state" vs running state. Rule 7: `show ` was hand-wavy and arguably invented syntax — conflicts with rule 5 ("do not invent CLI commands"). Replace with documented forms: `show ` (config mode, verified at `docs/cli.md:389`) or `show configuration commands` (op mode, verified at `docs/cli.md:224`). Both are direct quotes from the canonical CLI reference. 🤖 Generated by [robots](https://vyos.io)

docs: address review on context7 rules — op-mode set/add, edit-subtree

2026-05-10T17:43:52+00:00

Three corrections from Copilot review on #1946: Rule 2: Mode framing was technically wrong. `set ... ` is not unique to config mode — op mode has its own `set`/`add` commands for image management (`add system image`, `set system image default-boot`). Replace the `set/delete/show` listing with mode entry mechanics (`configure` enters config; op mode is the default after login) and acknowledge image-mgmt commands live in op mode. Rule 8: `add system image` and `set system image default-boot` are operational-mode commands (verified: docs/installation/update.md wraps `add system image` in `{opcmd}`; docs/installation/image.md does the same for `set system image default-boot`). The upgrade also is not in effect until reboot. Update to: op mode + reboot to activate. Rule 10: "Configuration is hierarchical — paths extend without re-stating it" was misleading. At the top level (just after `configure`), every `set`/`delete` line must include the full path. Relative paths only work inside an `edit ` context. The original phrasing would have led an LLM to omit parent nodes and emit invalid CLI examples. All revised rules verified ≤255 chars. 🤖 Generated by [robots](https://vyos.io)

docs: expand context7 rules — VyOS-specific LLM guardrails

2026-05-10T16:45:32+00:00

Add 5 rules to `context7.json` targeting recurring LLM mistakes when answering VyOS questions through the context7-served index: 1. `commit` vs `save` semantics + verification step. Most common mistake: forgetting that `set/delete` are staged-only, that `commit` runs validation (failure = no change), and that `save` is a separate persistence step. 2. Image-based, not package-managed. Stops `apt install ` recommendations. Upgrade is `add system image ` then `set system image default-boot `. 3. No raw Linux commands for configuration (`ip`, `iptables`, `systemctl`, NetworkManager). They bypass the CLI and do not persist. 4. CLI quoting with single quotes for whitespace/special chars + hierarchical-path reminder (paths under a parent extend without re-stating it). 5. Routing protocols are FRR-backed but only the VyOS-CLI-exposed subset is valid. Synthesizing from FRR docs produces invalid VyOS commands. Reinforces existing rule 5 with the most common synthesis trap. Each rule fits the 255-char per-rule limit. Total now 11 of 50. Lower-priority candidates intentionally omitted (low LLM-mistake yield): `compare`/`discard`/`rollback` mechanics, interface naming conventions, `commit-confirm`, `load`/`merge`, Equuleus EOL status — already implicit in the version-branches rule. 🤖 Generated by [robots](https://vyos.io)

chore: remove RST swap mechanism, archive rst-*.rst under docs/_rst_legacy/

2026-05-10T14:19:31+00:00

The swap mechanism (RST-as-fallback for migrated MD pages) is dormant — docs/_rst_overrides.txt has been empty since the MyST flip trio (#1899/#1900/#1901) landed in May 2026. The mechanism's surface area (scripts/swap_sources.py, its 245-line test, RTD pre/post hooks, Makefile glue, conf.py dynamic loader) is dead weight, and the rst-*.rst shadows scattered across the source tree cause Context7's parser to misclassify the project as RST. Changes: - Move 253 rst-*.rst shadow files into docs/_rst_legacy/ preserving subdirectory structure. They remain in the repo for reference; Sphinx excludes the folder via exclude_patterns; Context7 excludes it via excludeFolders. - Strip swap_sources.py invocation from docs/Makefile (swap/restore targets, : swap deps, trap chains). - Strip jobs: pre_build/post_build block from .readthedocs.yml. - Strip rst-*.rst exclude entry and the _md_exclude.txt loader from docs/conf.py; replace with a single _rst_legacy exclude. - Delete scripts/swap_sources.py, tests/test_swap_sources.py, docs/_rst_overrides.txt. - Update context7.json: add docs/_rst_legacy to excludeFolders; fix stale "Branch current tracks…" rule to "Branch rolling tracks…" (default branch was renamed 2026-05-10). - Update AGENTS.md: drop the "RST override mechanism" section and the test-runner snippet for the deleted test; describe _rst_legacy as archive only. Verified: sphinx-build -b html with --keep-going produces identical warning set (68 unique), identical sitemap entry count (257), identical llms.txt entry count (22), zero rst-* URLs in any artifact. 🤖 Generated by [robots](https://vyos.io)

docs(context7): pin previousVersions to release tags, not branches

2026-05-10T11:13:14+00:00

context7.json now references the floating release tags (1.5, 1.4) created by .github/workflows/update-version-tags.yml instead of the internal branch names (circinus, sagitta). The tags are kept at the HEAD of their corresponding branches by the workflow, so consumers get the same content under stable, version-shaped names. 🤖 Generated by [robots](https://vyos.io)

Enrich context7.json with project metadata, scope, and rules

2026-05-10T10:23:32+00:00

Adds the optional schema fields documented at https://context7.com/docs/adding-libraries to give the Context7 indexer clearer guidance: - projectTitle / description: stable display strings instead of LLM guesses on every refresh. - folders / excludeFolders / excludeFiles: limit indexing to docs/ and skip build artifacts, support scripts, and meta files. - rules: surface the conventions LLMs should respect when answering from VyOS docs — CLI mode separation, cfgcmd/opcmd authority, per-branch version mapping, no-invented-commands, and reserved documentation address space. - previousVersions: map circinus (1.5.x) and sagitta (1.4.x) so Context7 can serve version-appropriate answers. 🤖 Generated by [robots](https://vyos.io)

Add context7.json to claim repo ownership on context7.com

2026-05-10T10:08:37+00:00

Allows the repo owner to manage Context7 indexing settings (refresh cadence, exclusions, branding) for https://context7.com/vyos/vyos-documentation. 🤖 Generated by [robots](https://vyos.io)