Migrate open base-workspace issue and pull request titles to plain outcome wording #20

Problem

Open issues and pull requests in base-workspace still use category-prefixed titles. The accepted governance plan replaces that convention with plain outcome/problem titles after the new templates and repo profile are live. This repo-local train is tracked by Base governance tracker #2665.

Expected behavior

Inventory and rename every open issue and open pull request, including drafts, to plain outcome/problem wording after the new issue/PR templates and this repo's governance profile are active. Preserve closed issues and merged PR titles as historical records.

Scope and non-goals

Scope: Metadata-only title migration for open issues and PRs in base-workspace after Stage G gates.

Non-goals: Do not change issue body, labels, Type, Project values, milestone, status, branches, closed/merged titles or implementation content. Do not rename until #2667/#2669 contracts and [governance adoption issue #19] are active.

Affected areas

• Open issue/PR titles and repository Project item titles.
• Accepted source: governance plan #2664; issue form #2667; PR template #2669.
• Parent tracker: #2665.

Impact and evidence

1. Product intent: No behavior or product requirement changes.
2. Architecture and contracts: Applies the accepted title rule after the repo adoption gate.
3. User guidance: No user-facing content changes; cite the issue/PR inventory.
4. CLI/API and reference: No CLI/API surface changes.
5. Operations and safety: No branch or permission changes.
6. Validation and testing: Compare inventory counts and read back each changed title.
7. Examples and downstream use: Update only title examples that are part of this repository's active contributor guidance; otherwise give a no-impact reason.
8. Governance and contributor process: Applies the active plain-title rule without changing labels or issue types.
9. Decision records: No new decision; link to accepted decision in #2664.
10. Release notes: Reasoned none; repository metadata-only change has no product release note.

Open questions

• If a title's outcome is unclear, leave it unchanged and file a clarification issue rather than guessing.

Plan

• S1: One metadata-only PR for this repository.
• Dependencies: Base issue form #2667, Base PR template #2669 and [governance adoption issue Adopt the accepted governance profile in base-workspace #19]; see the tracker for rollout order.
• Acceptance criteria:
  • Inventory includes all open issues and PRs, including drafts, and excludes closed/merged items.
  • Every changed title is plain outcome/problem wording and preserves the issue's intent.
  • Before/after counts and old-to-new mapping are recorded; no other metadata is changed.
  • Ambiguous items are left unchanged and separately tracked.
• Validation: Read back changed GitHub titles; compare counts and samples; verify branches/links are unaffected.
• Risks and rollback: Title changes can disrupt searches; preserve an old-to-new mapping and revert incorrect titles exactly.
• Decision impact: No new decision is accepted.