rea-ci-tests-audit

Topics in the source

• REA CI and tests audit
• Establish the executed baseline
• Prove the failure or protection
• Assess efficiency without losing the gate
• Fix, verify, and hand off within scope

Establish which checks still catch real regressions and which costs can be removed without losing that protection. The outcome may be a verified fix, an evidence-backed recommendation, or an explicit decision to stop. Follow the checkout's AGENTS.md, testing guide, and contribution rules. Use their current commands and pinned toolchain, rather than commands remembered from an earlier audit. Preserve the requested scope: investigation alone does not authorize edits; this skill does not grant permission to publish issues, push, or merge. Existing user authorization still applies. Keep audit notes and raw results outside the tracked tree, normally in a task-specific /tmp directory. Fetch when the user asks for latest main. Pin the baseline SHA and inspected workflow revision; use an isolated worktree when changing or comparing code. Do not modify another task's checkout. Record dirty changes and the exact command, toolchain, host, selected tests, instrumentation, and prerequisites. An old run is evidence for its executed revision, even if main advances. Trace workflow triggers, changed-path selection, job dependencies, reusable actions, package scripts, test discovery, artifact produc

This is an excerpt. Refer to the complete source and its current requirements.