chore: follow felis to 105b0899 #1

Merged

natsukium merged 2 commits from follow-felis-105b0899 into main

2026-09-07 19:23:18 +09:00

natsukium commented

2026-09-07 17:08:25 +09:00

Owner

What

Advances vendor/felis from 06639a95 to felis main 105b0899 (1272
commits) and adapts the site to felis's further docs restructure.

Why felis changed what here

felis's docs/ tree kept moving since the last bump:

docs/backlog.md was migrated to Forgejo issues (open work is no longer
tracked as a doc page).
docs/research/ was dissolved into the Diátaxis quadrants (folded into
explanation/).
explanation/ grew architecture/, data-model/, protocols/, and
rendering/ subdirectories; reference/ grew a protocols/ subdirectory.
These autogenerate under the existing sidebar groups, so they needed no
config change.

src/content/docs/backlog.md and src/content/docs/research were symlinks
into paths that no longer exist in the vendored tree, so they went dangling
and the Astro content sync would fail on them. Removed the symlinks and the
Planning / Research notes sidebar groups in astro.config.mjs that
pointed at them, and fixed the one stale example route in README.md
(docs/spec.md moved under docs/reference/).

Also re-locked flake.lock: the committed lock still carried a stale
felis-web node left over from before the felis-web-component split (the
rename landed in flake.nix without a matching relock), and a newer
felis-web-component build (181870a1, 2026-08-23) has since been
published.

No other adaptation was needed — the rest of felis's changes in this range
(the published felis-cli JSON Schemas, IPC minor 10, felis daemon stop,
felis version, etc., per felis's CHANGELOG.md) are content facts inside
the vendored pages, not something this repo duplicates.

Verified

Via nix develop -c npm run <script> (the same commands .forgejo/workflows/ci.yml runs):

npm run check (astro check) — 0 errors, 0 warnings, 0 hints.
npm run build — 63 pages built, including the new
explanation/{architecture,data-model,protocols,rendering}/* and
reference/protocols/* routes.
npm run linkcheck (linkinator against dist/) — 72 internal links, all
resolved.

Left open

Nothing outstanding from this bump. The transitive felis input pulled in
by felis-web-component (via felis-web-gateway) still resolves to an
older felis revision than vendor/felis; that pin is felis-web-component's
own choice, not something this repo controls.

## What Advances `vendor/felis` from `06639a95` to felis main `105b0899` (1272 commits) and adapts the site to felis's further docs restructure. ## Why felis changed what here felis's `docs/` tree kept moving since the last bump: - `docs/backlog.md` was migrated to Forgejo issues (open work is no longer tracked as a doc page). - `docs/research/` was dissolved into the Diátaxis quadrants (folded into `explanation/`). - `explanation/` grew `architecture/`, `data-model/`, `protocols/`, and `rendering/` subdirectories; `reference/` grew a `protocols/` subdirectory. These autogenerate under the existing sidebar groups, so they needed no config change. `src/content/docs/backlog.md` and `src/content/docs/research` were symlinks into paths that no longer exist in the vendored tree, so they went dangling and the Astro content sync would fail on them. Removed the symlinks and the `Planning` / `Research notes` sidebar groups in `astro.config.mjs` that pointed at them, and fixed the one stale example route in `README.md` (`docs/spec.md` moved under `docs/reference/`). Also re-locked `flake.lock`: the committed lock still carried a stale `felis-web` node left over from before the `felis-web-component` split (the rename landed in `flake.nix` without a matching relock), and a newer `felis-web-component` build (`181870a1`, 2026-08-23) has since been published. No other adaptation was needed — the rest of felis's changes in this range (the published `felis-cli` JSON Schemas, IPC minor 10, `felis daemon stop`, `felis version`, etc., per felis's `CHANGELOG.md`) are content facts inside the vendored pages, not something this repo duplicates. ## Verified Via `nix develop -c npm run <script>` (the same commands `.forgejo/workflows/ci.yml` runs): - `npm run check` (astro check) — 0 errors, 0 warnings, 0 hints. - `npm run build` — 63 pages built, including the new `explanation/{architecture,data-model,protocols,rendering}/*` and `reference/protocols/*` routes. - `npm run linkcheck` (linkinator against `dist/`) — 72 internal links, all resolved. ## Left open Nothing outstanding from this bump. The transitive `felis` input pulled in by `felis-web-component` (via `felis-web-gateway`) still resolves to an older felis revision than `vendor/felis`; that pin is `felis-web-component`'s own choice, not something this repo controls.

natsukium added 2 commits

2026-09-07 17:08:25 +09:00

chore: advance the vendored felis submodule to 105b0899 fd36493abd

Picks up felis's further docs restructure (the reference/protocols and
explanation/{architecture,data-model,protocols,rendering} split), the
published felis-cli JSON Schemas, and IPC minor 10.

Re-lock the flake alongside it: the committed flake.lock still carried a
stale felis-web node left over from the felis-web-component split (flake.nix
already named felis-web-component, but the lock was never refreshed), and a
newer felis-web-component build has since been published.

docs: drop the backlog and research-notes sidebar groups

ci / astro check + link check (pull_request) Successful in 36s

Details

0d32ca93c5

felis migrated docs/backlog.md to Forgejo issues and dissolved
docs/research/ into the Diátaxis quadrants; both paths are gone from the
vendored tree, so the symlinks pointing at them and the sidebar groups
built around them are dangling. Fix the README's example route to the
page's new reference/ location too.

natsukium merged commit 2a70fdcc8f into main

2026-09-07 19:23:18 +09:00

natsukium deleted branch follow-felis-105b0899

2026-09-07 19:23:18 +09:00

natsukium referenced this pull request from a commit

2026-09-07 19:23:20 +09:00

chore: follow felis to 105b0899 (#1)