project-story-minerlisted

# Project Story Miner Turn project history into an evidence-backed narrative brief without inventing a cleaner story than the artifacts support. ## Set The Boundary Before searching, identify: - the repository or project in scope - the rough period, feature, incident, migration, or question - whether private/internal details may appear in a public draft - whether external systems such as GitHub issues or pull requests are in scope Use read-only inspection by default. Do not publish, message, edit source artifacts, or open external tickets unless the user separately asks. ## Build A Source Map Search the smallest relevant surface first, then widen only when the story remains unclear. 1. Read repository guidance, current documentation, changelogs, ADRs, plans, and benchmark notes. 2. Inspect the relevant code, tests, configuration, and commit history. 3. Trace high-value commits with `git show`; do not infer a journey from commit subjects alone. 4. Read linked issues, pull requests, review threads, or incident records when they are available and in scope. 5. Ask for author recollection only after the artifacts reveal which human details are genuinely missing. Useful local commands include: ```sh git log --all --date=short --format='%h %ad %s' -- path/to/scope git log --all --stat -- path/to/scope git show --stat --summary COMMIT git show COMMIT -- path/to/scope rg -n "benchmark|incident|decision|tradeoff|migration|regression|rollback" docs tests .github ``` Adapt com