grund 0.12.2

Added

• §FS-config.3.4.7: [[kinds]] scan = false — a non-citable kind that is listed in the generated Project map and not walked, for content that ships verbatim (scaffold templates, embedded assets, example configs). scan = false on a citable kind, on a kind with no home, and a [citations.<kind>] rule naming an unwalked kind are config errors; check --full still reaches the directory as out-of-scope territory, and grund config show prints the key where it is set. Decided in §DF-unwalked-kind-home. This repository lists templates/ that way. (PR #145)

Fixed

• §FS-config.3.4.7: scan = false kept the home out of the walk roots only, so a walk still read it on the way down from a root above it — docs/templates under an include = ["docs"] entry, or the config root — and [scan] include naming the home walked it outright. The key was a silent no-op for the layout it is most often written for. The home is now pruned wherever a walk meets it — folder and file homes alike, the latter never being a directory to skip — and a file in one is outside the configured scope under --full even when a walk root encloses it (§FS-check.3.14). (PR #146)

Changed

• This repository's examples/, .github/workflows/ and scripts/ are non-citable homes (§FS-config.3.4.1) — sh joins [scan] extensions so the shell scripts are checked — and every folder-kind index carries each declaration's own title sentence. The roadmap drops its fifteen shipped milestones: their record is the changelog and the spec each landed in, and everything that cited a milestone now cites that spec — code and decisions re-pointed, release notes keeping the milestone name as plain text. Open items name their GitHub issue where one exists. (PR #145)