Unblock required legacy lint status for GAIA map review candidate PR

[mdheller]

Summary

PR #69 is implemented and all visible GitHub Actions workflows are green, but merge is blocked by branch protection reporting required status check lint as expected.

Affected PR

• Add GAIA map workbench review candidate #69

Current green checks on head 05ec69d79bb38fedf517ca640e36d4114ecb47a2

• MeshRush Candidate: success
• validate: success
• lint: success
• ci: success

Additional diagnostic

The GitHub combined status API for the head commit returns no legacy status contexts. This suggests the branch protection rule may be expecting a legacy commit status named lint, while the repository currently emits GitHub Actions check runs.

Work already attempted

• Added the GAIA /map workbench review candidate.
• Validation passed.
• Renamed the lint workflow job from validate to lint on the PR branch to align the Actions check name with the required context.
• Merge remains blocked with: Required status check "lint" is expected.

Acceptance criteria

• Branch protection is updated to require the Actions check context that actually exists, or
• the repository emits the expected legacy lint status context, or
• maintainers explicitly merge using an approved administrative path.

Constraint

Do not weaken review or validation requirements. The candidate itself is advisory and evidence-only; this is a status-context wiring issue, not a code validation failure.