Release Tabellio v0.2.0 and finish GitHub-only migration

[hudsonaikins]

Summary

• prepare @intelip/tabellio version 0.2.0
• remove the retired one-time Forgejo migration reader, CLI command, tests, fixtures, and documentation
• classify all 34 inherited Fallow interface findings and add narrow method-level suppressions for proven contract/override false positives
• leave the current tree with zero Forgejo/Gitea references and zero Fallow dead-code findings

Evidence

• commit: 532072cceb70e64078d05af10299f7b18a7ba279
• Entire checkpoint: a23449f406cf
• validation run: validation-1e26770a-6cb9-4a28-bb33-cd3e87672e9c
• validation result: commits/532072cceb70e64078d05af10299f7b18a7ba279/validation-1e26770a-6cb9-4a28-bb33-cd3e87672e9c.json
• validation/control state published atomically to the private GitHub control repository

Checks

• npm run check: passed, 71 tests
• exact-head tabellio-validate: passed
• Fallow dead-code scan: 0 findings
• Fallow stale suppressions: 0
• Fallow changed-code audit against origin/main: passed with 0 introduced or inherited dead-code findings
• Fallow fix dry-run: 0 fixes
• npm pack --dry-run --json: passed, 101 package entries, version 0.2.0
• git diff --check: passed
• retired migrate command probe: passed
• current-tree Forgejo/Gitea search: 0 matches

External-action policy

• GitHub code branch push: approved and completed
• private control repository settings hardening: approved and completed
• private control-ref publication: approved and completed
• obsolete local recovery branch deletion: approved and completed
• GitHub pull request, squash merge, tag, and release: approved as this release workflow
• deployment, billing, DNS/hosting, infrastructure, database migration, secret-value reads: not attempted
• npm publication: not authorized and not planned

Review focus

• confirm removal is limited to the retired v0.1 migration bridge; historical recovery remains in Git history
• confirm each Fallow suppression is attached only to an actual interface/override contract method
• confirm changelog accurately describes the GitHub-only boundary and v0.2.0 release

Skipped checks

• none