v0.2.0

• fix(skills): eval example cites a source of truth, not a dated plan path
• chore: release specfold 0.2.0
• chore: plain gitignore for build output and local files
• feat(skills): usage skills shipped with the package; root allowlist gitignore
• docs: install instructions written for people
• feat(npm): ship the CLI on npm as @modootoday/specfold
• fix(files): command stores run from the repository root
• feat(import): wrap raw files into generated documents; drop old-layout files
• fix(import): chapters and attachments move, not copy
• fix(import): nested bundles stay with their first rule; stem aliases; path targets keep .md
• fix(import, links): chapter aliases, clean relation targets, relative paths, external notes
• perf: guards and checks read only what changed, once
• fix(guards): an empty published path is a hit, not a clean pass
• test: neutral fixtures in guard tests (no Korean text, no home paths)
• feat(guards): published-path scope, path patterns, lookaround, script and code exemptions
• refactor: one responsibility per file, context directories, no flat roots
• feat(guards): self-tests, table patterns, allow lists, gzip, empty-scan and baseline
• feat(check): V1 finds published paths, not only configured ones
• feat(check): L6, citations outside documents still resolve
• feat(check): T4, an edited body moves its updated date
• feat(check): baseline of known findings, strict paths, per-rule severity, --fail-on
• feat: configurable transitions, status-required fields, supersede cycles, verify runner
• fix(import): stub-only redirects, home owner fallback, nested history, gitignore globs
• docs: use neutral example paths (services/, research) in docs and tests
• ci: name the release approval environment after its registry (crates)
• feat: first version of specfold