docs: fix stale issue numbers in archetype gap audit

The audit draft was written before the GitHub API assigned the actual
issue numbers. It referenced 'issue #97' in three places for the
plain-Product-Manager follow-up. The real issue number is #90
(verified via gh issue view).

- Line 135: 'issue #97, see footer' -> 'issue #90, see footer'
- Line 194: 'Filed as issue #97' -> 'Filed as issue #90'
- Line 204: 'follow-up to #97' -> 'follow-up to #90'

Also caught by this rebase onto latest main (docs: align repository
documentation with MVP status, PR #88). The rebase was conflict-free
because PR #88 and the audit modified orthogonal sections of the
shared files (README.md, docs/MVP_RELEASE_STATUS.md, and
docs/PR_CLEANUP_HANDOFF.md).

The rebase confirmed that all five audit findings survived intact:

- core registry has 7 live archetypes
- intelligence registry has 3 archetypes
- plain Product Manager is missing from core
- #90 tracks plain Product Manager
- #91 tracks registry consolidation

No code changes. Docs only. PR #37 and PR #78 untouched.

Validates: pnpm test 12/12, pnpm lint 0 errors, pnpm build 6/6.

Author: Cleanup Bot

docs/ARCHETYPE_GAP_AUDIT.md

@@ -132,7 +132,7 @@ registries being out of sync — is filed as a follow-up issue and
 | Data Scientist / Analytics Engineer | Issue #40 | ❌ Missing | |
 | Engineering Manager | Issue #41 | ❌ Missing | |
 | Product Designer / UX Researcher | Issue #42 | ❌ Missing | |
-| **Product Manager** *(plain, non-AI)* | **NEW — created by this audit (issue #97, see footer)** | ❌ Missing from `core` | `intelligence` has it. **This is the biggest live-system gap — see below.** |
+| **Product Manager** *(plain, non-AI)* | **NEW — created by this audit (issue #90, see footer)** | ❌ Missing from `core` | `intelligence` has it. **This is the biggest live-system gap — see below.** |
 | Classic ML Engineer | `scripts/create-issues.sh` line 47 | ❌ Missing | Same as issue #3. |
 | Data Analyst / Business Analyst | Community baseline (see *Community needs* below) | ❌ Missing | Partial coverage via `core.data-engineer` and issue #40. |
 | Project Manager / Scrum Master | Community baseline | ❌ Missing | Adjacent to TPM (issue #6) and Engineering Manager (issue #41). |
@@ -191,7 +191,7 @@ prefers it when AI-PM keywords don't fire — would close this gap.
 
 | # | Gap | Severity | Effort | Notes |
 |---|---|---|---|---|
-| 1 | `core` registry missing plain `product-manager`; live detector fallback to `backend-engineer` for non-AI PM CVs | **High** | Small–Medium | Filed as issue #97. New `core` archetype + small `detectArchetype` priority tweak. |
+| 1 | `core` registry missing plain `product-manager`; live detector fallback to `backend-engineer` for non-AI PM CVs | **High** | Small–Medium | Filed as issue #90. New `core` archetype + small `detectArchetype` priority tweak. |
 | 2 | Duplicate archetype registries (`core` vs `intelligence`) with divergent schemas | **High** (architectural) | Medium–Large | Filed as follow-up issue (consolidation). Affects types, prompts, eval fixtures, skill. NOT done in this PR. |
 | 3 | `intelligence` registry has only 3 archetypes; V1 scope targets 3–5 | Low | Small | Add Full-stack Engineer and UX/UI Designer into `intelligence` too if/when the consolidation happens. |
 | 4 | 11 existing open archetype issues (Mobile, Security, ML, Full-Stack, TPM, UX, Cloud, Data Scientist, Engineering Manager, Product Designer, AI Engineer, AI PM) have no owner | Medium | Various | All already filed. Community can pick via `good first issue`. |
@@ -201,7 +201,7 @@ prefers it when AI-PM keywords don't fire — would close this gap.
 ## Recommended priority order for follow-up PRs
 
 1. **Add plain `product-manager` to `core`** — small, scoped, fixes the
-   live detection for non-AI PMs. Issue: follow-up to #97 (when
+   live detection for non-AI PMs. Issue: follow-up to #90 (when
    created, see footer).
 2. **Consolidate the two registries** — make `core`'s detect / evaluator
    consume `intelligence`'s `Archetype` directly (or vice-versa). This