[Stage 2.1] Review Stage 3 blocked labels after readiness gate

[Will-thom]

Goal

Review Stage 3 issues labeled status: blocked after the Stage 2.1 hardening/readiness gate is completed, then unblock the first safe design issues.

Context

Most Stage 3 implementation issues are intentionally blocked until the MVP hardening work and Stage 3 readiness gate are complete. After Stage 2.1 closes the release/validation gaps, maintainers should update issue status labels so contributors know what can start next.

Acceptance Criteria

• Review all open Stage 3 issues labeled status: blocked.
• Keep implementation-heavy issues blocked when they still depend on design contracts, mocks, or acceptance gates.
• Move early planning/design issues to status: ready when dependencies are satisfied.
• Leave a short maintainer comment on issues whose status changes, explaining why they were unblocked or kept blocked.
• Confirm no open issue is missing a stage label, area label, and status label.
• Reference the Stage 3 acceptance checklist and visual dependency map once those issues exist.

Suggested Dependencies

• [Stage 2.1] Define Stage 3 readiness gate #79 Define Stage 3 readiness gate
• [Stage 3] Define v0.3.0 release acceptance checklist #100 Define v0.3.0 release acceptance checklist
• [Stage 3] Add visual dependency map for provider-context backlog #101 Add visual dependency map for provider-context backlog

Notes For Contributors

This is maintainer/backlog hygiene. It should not change production code.

[github-actions]

Hi @Will-thom, thank you for contributing to PR Maven CLI.

I appreciate the time you spent opening this issue. This project is intentionally shaped for focused, reviewable open source contributions, so your input helps the tool become more useful for Java and Maven teams.

A maintainer will review the context, labels, and next steps as soon as possible. If this is your first contribution here, welcome aboard.

Useful links:

• Contributing guide: CONTRIBUTING.md
• Testing guide: docs/testing.md
• CI/CD guide: docs/ci.md

Thank you for helping build a deterministic, local-first Maven failure triage tool.