✨ Render feature-store manifest in collapsible#144
Merged
Conversation
bdsoha
force-pushed
the
feature/fs-manifest-partial
branch
from
0e8c85f to
41d1b6d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scripts/generate-fs-manifest.mjsrendersdocs/partials/fs-manifest.mdfrom.vitepress/data/fs-manifest.json. Two tables (apt + artifact) grouped bytype, sorted by name case-insensitive. Handles missing data file with a placeholder line.scripts/generate-all.mjs.docs/editor/features.mdgets a vitepress collapsible::: details Feature Store Inventoryblock directly below the existing static## Available Featurestable (default closed). Static table is preserved verbatim — the collapsible is additive.docs/partials/fs-manifest.mdis gitignored to match the existing partial convention (dependencies.md/extensions.md/etc.).Story
ws-bmadstory2026-q2.30 — feature-store manifest publish. Data file (.vitepress/data/fs-manifest.json) arrives via the ws-meta distribute workflow — a sync PR should be auto-opened against this repo shortly afterkloudkit/ws-meta#47merges.Test plan
yarn run docs:buildsucceeds (generator's placeholder branch handles the missing data file pre-sync)