ci: add Woodpecker WorldOS Linux gates

[100yenadmin]

Summary

Refs #1166.
Refs #1165.

This PR adds the Woodpecker-side Linux CI definitions for the five currently required WorldOS branch-protection gates:

• test
• viewer-tests
• qa-release-gate-tests
• server-contracts
• license-check

It keeps GitHub Actions workflows in place for now. Branch protection should not be changed until Woodpecker runs on this PR head and GitHub receives the exact replacement status contexts.

Renderer cleanup

• Quarantines the Godot lane as reference/extension material instead of current required renderer work.
• Keeps .github/workflows/godot.yml as a reference/extension workflow, not a required emergency Woodpecker gate.
• Updates onboarding/runbook/roadmap language to point current visual renderer work at the Unity 6 / Unity-MCP GPU-VM lane.
• Leaves the actual render-profile.schema.json contract unchanged; Unity-current work consumes core/SceneGrid today, and a formal unity{} block remains a future contract change.

Validation

• git diff --check
• Parsed all .woodpecker/*.yml with PyYAML.
• python3 scripts/license_check.py
• Read-only adversarial review:
  • Fixed missing git in the python:3.12-slim license-check container.
  • Fixed stale Godot onboarding/source-of-truth language.
  • Documented qa/test_visual_critic.py as an intentional deterministic current-renderer addition to the parity set.

Known rollout blocker

Woodpecker activation for electricsheephq/WorldOS is still blocked before this PR can prove statuses:

• WorldOS is visible in Woodpecker but inactive.
• POST /api/repos?forge_remote_id=1246787955 returned could not create webhook in forge.
• Existing branch protection still requires the old GitHub Actions app-scoped contexts: test, viewer-tests, qa-release-gate-tests, server-contracts, license-check.

No branch-protection change is included in this PR. The next safe step is to repair Woodpecker forge/webhook activation, run these workflows on the PR SHA, capture the exact GitHub status contexts, and only then update required checks.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: aa398a16-ad61-4040-b945-d661177c74f5

📥 Commits

Reviewing files that changed from the base of the PR and between f433e7c and 2c52057.

📒 Files selected for processing (15)

• .claude/skills/godot-dev/SKILL.md
• .github/workflows/godot.yml
• .woodpecker/license-check.yml
• .woodpecker/qa-release-gate-tests.yml
• .woodpecker/server-contracts.yml
• .woodpecker/test.yml
• .woodpecker/viewer-tests.yml
• WorldOS-RUNBOOK.md
• docs/GETTING_STARTED.md
• docs/qa/TEST_MATRIX.md
• docs/roadmap/WORLDOS-GRAPHICS-ROADMAP.md
• docs/roadmap/contracts/render-profile.md
• godot/HANDOFF.md
• qa/lib_beat_driver.sh
• servers/engine/tests/test_scorer_integrity.py

---

📝 Walkthrough

Priority Level: P4/NIT

• The PR’s main CI change is the addition of Woodpecker Linux pipelines for the required WorldOS gates (test, viewer-tests, qa-release-gate-tests, server-contracts, license-check), while keeping GitHub Actions in place until Woodpecker is active and status contexts are mirrored.
• Renderer documentation was updated to make Unity 6 / Unity-MCP the current visual-renderer path and reframe Godot as reference/quarantined material; the render-profile contract itself was left unchanged.
• Validation noted in the PR includes git diff --check, Woodpecker YAML parsing, and python3 scripts/license_check.py.

No P0-P3 issues found.

Walkthrough

The PR reclassifies Godot GT2 material as reference-only, moves GT2 guidance toward Unity 6 / Unity-MCP and current-renderer docs, adds several Woodpecker CI pipelines for server, viewer, license, and QA checks, and updates two test utilities.

Changes

GT2 renderer lane and CI updates

Layer / File(s)	Summary
GT2 renderer direction and contract docs docs/roadmap/contracts/render-profile.md, docs/roadmap/WORLDOS-GRAPHICS-ROADMAP.md, WorldOS-RUNBOOK.md, docs/GETTING_STARTED.md, docs/qa/TEST_MATRIX.md	render-profile, roadmap, runbook, getting-started, and test-matrix text now describe Unity 6 / Unity-MCP as the current GT2 visual renderer direction and reframe Godot as reference or extension material.
Godot reference lane docs .claude/skills/godot-dev/SKILL.md, .github/workflows/godot.yml, godot/HANDOFF.md	The Godot dev skill, workflow comment, and handoff docs now restrict usage to explicit godot/ reference or extension work and describe the material as quarantined historical/reference content pending issue 1165.
Woodpecker pipelines .woodpecker/*.yml	New Woodpecker pipelines add license checking, server contract tests, release-gate QA tests, server test coverage, and viewer tests, each handling pull-request merge-ref checkout before running its commands.
Test harness and scorer assertions qa/lib_beat_driver.sh, servers/engine/tests/test_scorer_integrity.py	The removable-volume cleanup script now preserves PATH, and the scorer integrity test parses [duo] done. key-value output before asserting lens scores.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related issues

• electricsheephq/WorldOS issue 1166: The new Woodpecker pipelines and required-check language match the CI/branch-protection changes described there.
• electricsheephq/WorldOS issue 1165: The Godot quarantine, reference-only framing, and Unity/current-renderer redirection align with that renderer-direction issue.

Possibly related PRs

• electricsheephq/WorldOS#403: Both PRs add viewer test CI coverage, including pytest viewer/tests.
• electricsheephq/WorldOS#1066: Both PRs touch the same render-profile Godot/reference contract wording.
• electricsheephq/WorldOS#1094: Both PRs rework godot/HANDOFF.md into status/reference documentation.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/woodpecker-ci-worldos-20260625

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.