The starter profile/README.md from vole admin init repeated the landing page
heading (# <instance_name>), so the home page showed the forge name twice,
and the file said nothing about how to replace the text or where the other
instance files live.
This drops the header — the page already renders instance_name — and replaces
it with one line naming profile/README.md as the file to edit plus a link to
the instance repository’s own overview at /r/<instance_repo>. The name comes
from the configured instance_repo, not a hard-coded vole-instance.
Template and Ensure now take the repository name instead of the instance
name, which the template no longer uses; both callers are updated. Existing
repositories with history are untouched.
Testing
go build ./...go test -tags sqlite_fts5 ./forge/..../vole workflow run verify— ok: 1 job
New forge/instancerepo/seed_test.go asserts the starter has no heading, links
to /r/<repo>, and degrades to plain text when no repository name is available.