Adds .devfoundry/skills/new-project-reset.md: a one-time, explicitly-triggered
procedure for clearing DevFoundry's own internal process-development history
(specs/archive/, specs/active/, specs/.spec-counter, improvement-log.md
entries, and any residual project-specific facts in .devfoundry/references/)
when this template is copied to start a real project. It never runs
automatically or as part of the normal per-spec Archive step (AGENTS.md
Collaboration Rule 6 makes that explicit).

The skill was authored but deliberately not run against this repo - the
archive still holds SPEC-001 through SPEC-006 intact.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

SPEC-004 vendored RouteKit into the repo, configured IIS Express, ran real
migrations, and executed the full aspunit suite (26/26 passing against a
live running site) to prove the TDD/Design-by-Contract/MVC/QA rules actually
hold up against real code, not just documentation specs. It also fixed a
real IIS Express multi-site startup bug and excluded leftover domain-specific
artifacts found in the "generic" upstream starter.

SPEC-005 reverted the vendored application once that was proven: DevFoundry
is meant to stay a reusable process template, not host one project's live
app instance. The reusable findings (leftover-artifact risk when vendoring,
IIS Express one-process-per-site requirement) stayed in
asp-classic-framework.md; environments.md reverted to blank placeholders;
README/CLAUDE.md gained a note to keep this repo application-code-free.

Both retrospectives are logged in improvement-log.md (reference-gap,
interview-gap) with the friction tally updated accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>