wiki-ingest

# Wiki Ingest <skill_contract> <input>Accessible PDF, URL, transcript, clipping, or note plus vault root, topic, provenance, permissions, and lifecycle context.</input> <output>Immutable source evidence, linked concept and entity updates, navigation and lifecycle changes, and a verified ingest receipt.</output> <done>Touched files pass source, link, block-ref, frontmatter, lifecycle, understanding, and read-after-write checks.</done> <non_goals>Fabricated provenance, source mutation, raw-summary dumping, unsupported rule promotion, or unverified completion.</non_goals> Use STOW: **Source -> Transform -> Organize -> Write-back**. The source is evidence, the concept page is current understanding, and the log is the receipt. Load `references/stow-contract.md` for schemas and lifecycle details. ## Usage Template Provide: source path/URL/note, vault root, intended topic, permissions, and whether the item came from a clipping queue. Optional: path config, prior canonical source, and desired behavior/skill candidate. ## Workflow <intake> 1. Verify source existence, type, accessibility, date, and vault identity. 2. Resolve configured directories; record defaults only when no config exists. 3. Classify input as external fact, human experience, internal state, or environment signal. 4. Assign source risk based on primary/secondary/mediated/self-reported status and freshness. 5. Derive a source identity from canonical URL or source id, then hash/title/date fallbacks. S...