[OPS-01] Make GitHub Issues the enforced source of truth

[dkritarth]

Outcome

Replace wiki-card task selection with an authoritative, phased, dependency-locked GitHub Issues workflow and publish current documentation changes.

Why

Repository had no issues while implementation PRs referenced wiki cards and claimed completion from mocked/unit checks. Agents could start later work without independently proving earlier behavior. Current product direction and verification contract were fragmented across stale documents.

Scope

• Personal product goal and Codex-first priority in root guidance.
• GitHub Issues as sole executable backlog.
• Four milestones, phase/status/area labels, and detailed issues [S0-01] Prove Codex ACP against current signed-in subscription #25–[G3] Gate: certify advanced research workflow #47.
• Explicit dependency chain and gate issues.
• Existing PRs P2-01: Notes tab — per-paper markdown notes (SQLite) #21–P2-04: ORCID author badges #24 linked to issues [R1-01] Verify and finish per-paper Notes workflow #29–[R1-04] Verify and finish ORCID author evidence #32 and marked blocked.
• Structured task issue form and PR evidence template.
• CI gate requiring exactly one closing issue, allowed status, and verification sections.
• Wiki clearly marked historical.

Acceptance criteria

• Root docs consistently identify GitHub Issues as sole task authority.
• Exactly one issue ([S0-01] Prove Codex ACP against current signed-in subscription #25) is ready; [S0-02] Audit complete real-paper Electron journey and record every failure #26–[G3] Gate: certify advanced research workflow #47 are blocked.
• Issues carry milestones, dependencies, acceptance criteria, live procedure, and evidence requirements.
• PRs P2-01: Notes tab — per-paper markdown notes (SQLite) #21–P2-04: ORCID author badges #24 close correct issues and preserve stacked merge order.
• New issue form defaults work to blocked.
• PR CI rejects blocked/unlinked/under-evidenced changes.
• Wiki and repository documentation changes are pushed.
• YAML and Markdown/diff checks pass.
• Branch protection requires issue gate after workflow lands.

Verification

• Parse every YAML file.
• Run git diff --check in repository and wiki.
• Query all issue labels/milestones/bodies from GitHub.
• Query PR P2-01: Notes tab — per-paper markdown notes (SQLite) #21–P2-04: ORCID author badges #24 bases, closing lines, and blocked labels.
• Open, check, and merge governance PR through protected master.
• Confirm required status check in branch protection after merge.

Live limitation

This governance change does not claim application behavior works. Issue #25 begins product verification.

PR evidence

PR must use Closes #48, list created GitHub objects, include validation outputs, and disclose that application tests are unchanged because only documentation/workflow files changed.