WP-prompt canonical hygiene: rename /ad-hoc-profile-load → /spk-load-profile via new forward migration

[stijn-dejongh]

WP-prompt canonical hygiene: rename /ad-hoc-profile-load → /spk-load-profile

Task · Milestone: 3.2.6 · Priority: P3 (LOW) · Parent epic: #3809

Context

Software-dev WP source templates reference the legacy alias /ad-hoc-profile-load
(canonical is spk-doctrine-profile-load; the alias is test-locked and resolves correctly
— this is canonical-naming drift, LOW, not a defect). Note: ad-hoc-load (no -profile)
is a strawman — 0 hits; the real token is /ad-hoc-profile-load.

References to rename (/ad-hoc-profile-load → /spk-load-profile, keeping the leading slash):

• packs/built-in/missions/software-dev/templates/task-prompt-template.md:31
• the implement / review / tasks(-packages) prompts
• reviewer-implementer-role-separation.tactic.yaml:26
• the rc35 handoff migration references

Constraints (§4.4)

• EXCLUDE the alias-declaring surfaces — they are test-locked; editing them goes red:
  • spk-doctrine-profile-load/SKILL.md:35
  • src/doctrine/skills/README.md:116
• Do it via a NEW forward migration, not by editing the shipped rc35 migration in place
  (mutating already-emitted text diverges already-migrated installs).
• Gate on pytest tests/doctrine/test_spk_skill_pack.py.
• Depends on /spk-load-profile existing (/spk-load-profile <id> <instructions> consolidation primitive #3812).

Milestone call

Kept in 3.2.6 (P3, LOW/optional) to honour the design doc's own §5 scope table, which lists
§4.4 in the "In 3.2.6" column. It is optional hygiene — a maintainer may defer it to Product
backlog without harm. Under the doctrine-surface freeze it is a natural candidate to land last.

Source of truth

• docs/architecture/profile-load-reliability.md §3, §4.4

Freeze note. WP templates + tactic are doctrine surfaces; likely pr:deferred under the
3.2.x doctrine-surface freeze. Sequence after the activation-data fix and /spk-load-profile.