Clean up stale milestone wording in README and CONTRIBUTING

[Aggredicus]

Clean up stale milestone wording in README and CONTRIBUTING

Purpose

Remove or update stale wording now that Issue #2 has been completed and the repository has moved beyond the initial v0.1 scaffold/handoff phase.

This keeps human and AI contributors from following outdated instructions.

Scope

Review and update:

README.md
CONTRIBUTING.md
docs/developer-handoff.md

Known cleanup candidates:

• CONTRIBUTING.md still says Issue Codify branching and AI coding quality workflow #2 should be completed before v0.2 work.
• README still frames the current milestone as v0.1 target even though v0.2 planning is underway.
• Handoff docs may need a short note that Issue Codify branching and AI coding quality workflow #2 is complete and Issue Enable main branch protection and required CI checks #5/v0.2.0: Add response policy, rate limits, and MORE pagination #1 are the next priorities.

Non-goals

Do not change runtime behavior.
Do not rewrite the docs from scratch.
Do not implement Issue #1.

Acceptance criteria

• Stale Issue Codify branching and AI coding quality workflow #2 wording is removed or updated.
• README current-status language reflects the actual current phase.
• CONTRIBUTING points to the current workflow without outdated sequencing.
• Developer handoff docs are still accurate.
• No safety rules are weakened.

Rollback plan

Revert the wording updates if they create confusion.

[qorexdevs]

I can take this one. Plan: update README and CONTRIBUTING milestone wording to match the current roadmap, then do a quick link/path pass so references stay correct. If that scope works, please assign #17 to me.

[Aggredicus]

Closing as completed. The stale milestone wording was addressed by consolidated docs cleanup in PR #39 and finalized by merged PR #48.