Connect DEV readiness evaluator to live GitHub Project

[syllik]

Problem

The DEV readiness policy is implemented and tested, but it currently evaluates fixtures only. It does not read live GitHub Issues, Development-linked PRs, native dependencies, Organization Issue Fields, or Project #5 state, and it cannot update Project Status.

Outcome

Connect the existing evaluator to real ChipIn GitHub state, validate its decisions in read-only mode, then enable the narrowly scoped automatic Project transition → DEV.

Scope

1. Add a read-only adapter for the live GitHub state required by the evaluator.
2. Read canonical task metadata and Project Moved: global Node.js and GitHub Actions runtime upgrade #5 Status without inferring missing values.
3. Resolve native parent/sub-issue and blocking relationships.
4. Resolve Development-linked PR integration against repository-specific branches:
   • frontend → dev
   • backend → develop
   • knowledge base → main
5. Run/report readiness decisions against real representative issues without mutations.
6. Verify fail-closed behavior for missing, unreadable, ambiguous, or inconsistent state.
7. Only after read-only verification, add the minimum write path required to move an eligible item to DEV.

Safety

• Do not automate PROD, Done, issue closure, product-parent closure, or status regression in v1.
• Do not infer Organization Issue Fields from legacy labels/milestones.
• Do not treat plain URLs or informational References as workflow relationships.
• Ambiguous state must block mutation.
• Keep permissions minimal; separate read-only verification from the mutation step.

Acceptance

• Live adapter feeds real Issue/PR/Project state into the existing evaluator.
• Representative FE, BE and KB cases are verified read-only against expected decisions.
• Missing/ambiguous state fails closed.
• Reopened/changed required work after DEV is reported as inconsistent, not auto-regressed.
• Eligible work can be moved automatically to DEV only after read-only verification passes.
• PROD, Done, issue/parent closure and regression remain manual.
• Automated tests cover adapter normalization and mutation guardrails.

References

• Policy/evaluator: https://github.com/ChipIn-one/.github/tree/main/automation
• Canonical issue schema: https://github.com/ChipIn-one/.github/blob/main/github-issue-schema.md
• Tracking migration: Migrate task tracking from Trello to GitHub Issues chipin-frontend#164
• Evaluator implementation PR: feat(automation): add DEV readiness policy evaluator #4