The bug report template asks for steps that don't reference the removed CLI

## Summary

`.github/ISSUE_TEMPLATE/bug-report.yml` still instructs reporters to run
`woodland-gen`, a binary that does not exist at HEAD. Every bug reporter
hits an unsatisfiable instruction.

## Motivation

Three places in the template:

- `:14` — example title, "woodland-gen character emits duplicate names
for bird faction".
- `:32` — reproduction steps, "1. Run `woodland-gen character --faction
bird --seed 42`".
- `:62` — the version field is prefilled with
``woodland-gen: 0.2.0 (run `woodland-gen --version`)``.

There is no `bin` key in any of the four manifests and no `cli` script;
`CLAUDE.md` states this outright ("No CLI binary is wired up at HEAD…
there is no `bin`, `cli.ts`, or `cli` script").

#357 fixed exactly this staleness in `README.md` and closed. The issue
templates were not in its scope, so the last surface still advertising
the retired CLI is the one a reporter is required to fill in — and the
version field asks them to run a command that cannot succeed, which is
where they stop.

## Scope

- Replace the example title, reproduction steps, and version-field
placeholder with the Foundry module flow the repository actually ships.
- Check `feature-request.yml` and `work-item.yml` for the same staleness
while the file is open.

## Acceptance criteria

- [ ] `grep -rn woodland-gen .github/ISSUE_TEMPLATE/` returns nothing, or
only text marked as historical.
- [ ] The version field asks for something a reporter can actually
determine.
- [ ] vale and markdownlint pass.

## Additional context

- Completes the sweep #357 started for `README.md`; the same class of
staleness was fixed in `CLAUDE.md` by #310 / PR #356.
- Found while surveying this repository's conventions to scaffold a new
TypeScript project.