grund 0.13.1

Added

• Report intake: .github/ISSUE_TEMPLATE/ carries four GitHub issue forms — bug report, feature request, usability report, and token or time waste — each applying the matching kind label (bug, enhancement, usability, tokens) as the issue is opened, and config.yml turns blank issues off so no issue can arrive without a kind. Every form asks for the fields that make a report actionable: the context (command, directory, version), what happened, what was expected, an optional workaround, and, for the token form, the cost. (PR #205)
• §FS-values, §DA-explicit-value-bindings: add opt-in first-class Markdown and home-JSON values, exact authored bindings in prose and scanned comments, arbitrary-precision decimal or decoded-string consistency checks, fixed text/NDJSON diagnostics, and shared query, formatter, workspace, core, and LSP behavior. Repositories opt in per citable kind with only values = true; existing repositories keep byte-identical behavior. Closes issues #37 and #38. (PR #206)
• §FS-config.3.2, §FS-check.3.19, §FS-show.2.2: add opt-in explicit named section coordinates across checking, queries, references, formatting, completion, LSP, and generated guidance. [id] named_sections = true makes complete colon-form handles such as goals.performance stable and addressable at every depth, permits ordered numeric children such as goals.3, reserves number.name, and reports missing prefixes instead of accepting structurally orphaned paths. The absent/false default retains numeric behavior and output; grund init writes named_sections = false. (PR #204)