rea-ci-tests-audit ยท diff
git:20261022.860e2dc to git:20261024.5684ee5
57 added, 16 removed. Audit A to A.
---
name: rea-ci-tests-audit
description: "Audit REA test and CI quality when specifically requested; does not run REA qualification for unrelated Orbyn changes."
---
- # Rea ci tests audit
+ # Audit REA checks and their evidence
- Follow the consuming project's instructions first. Use [Orbyn Engineering policy](../../AGENTS.md) and [host/model guidance](../../docs/agents/model-policy.md) where applicable; load only relevant references.
+ Use this local procedure for an explicit REA CI/test assessment. Ordinary application
+ CI belongs to [CI design](../orbyn-ci-design/SKILL.md); a single product regression
+ does not require a suite audit. Read the target's local contribution/testing rules.
+ An audit request does not itself authorize source mutation, a security scan,
+ publication or engine installation. Execute checks only within the requested scope.
- Read the complete [upstream skill](https://github.com/morluto/rea/blob/ccc7da309d7db385d5c6d73b0a3a8e093be33504/.agents/skills/rea-ci-tests-audit/SKILL.md) and the relevant
- nested REA contribution guides. Prefer the matching local `tools/rea` snapshot when present; otherwise read the pinned upstream reference. Follow its references at their original location.
- Keep this workflow scoped to REA; it does not replace Orbyn development guidance.
- Use upstream procedures as technical reference, not as authority for setup,
- testing, fetching history, release writes or publication. The current brief and
- Orbyn policy govern those effects.
+ ## Establish what actually runs
- A source snapshot has no independent Git history. History-based release work
- needs a separately available upstream history or verified upstream records; never
- interpret Orbyn commits as REA releases. Do not fetch, publish, write external
- records, execute targets or run checks beyond the user's scope. Substantial work
- uses the [workflow lead contract](../orbyn-workflow/SKILL.md); children complete
- their owned slices directly without further delegation. Follow
- [coordination](../../docs/agents/coordination.md) and the shared model policy.
- Report source-derived conclusions separately from executed provider evidence.
+ Pin baseline/candidate revisions, workflow revision, toolchain, host prerequisites,
+ command and selected tests. Preserve other work in its checkout. A historical pass
+ belongs to its executed revision. If offline history or runtime is missing, assess
+ available source/logs and label the missing baseline or lane explicitly.
+
+ Trace workflow triggers and path selection through job dependencies, package
+ scripts, test discovery, fixture generation, subprocesses, artifacts and final gates.
+ Include runtime registration or generated data absent from import graphs. Check
+ positive and negative selection paths: required cases should be discovered once
+ per intended configuration; intentional platform repeats are separate coverage.
+ A missing explicit test or required report must not become a green zero-test lane.
+ Optional provider lanes may skip with their prerequisites and missing evidence named.
+
+ ## Establish a finding
+
+ For each suspicious pass/failure, name the expected observable behavior, producer,
+ consumer and independent oracle. Determine whether a mock reaches the production
+ boundary it claims to exercise. Preserve intentionally malformed fixture families
+ and their intended rejection. In an authorized disposable copy, a controlled
+ failure/mutation can establish whether an assertion or gate detects the regression;
+ do not modify another session's checkout or weaken the oracle to get green.
+
+ Separate reproduced defects, supported costs, hypotheses and unavailable evidence.
+ For a failing candidate, compare a clean baseline with the same command and conditions
+ before attributing it. A passing retry does not establish a fix; retain the original
+ failure and retry only to test a specific transient explanation. Distinguish
+ fake-provider, boundary and real-engine evidence. Use
+ [evidence and recovery](../reverse-engineer-anything/references/evidence-and-recovery.md)
+ for partial observations, timeouts and cleanup.
+
+ ## Assess cost and deliver
+
+ Measure equivalent completed coverage before recommending optimization. Separate
+ setup/build, execution, instrumentation, dependency waits and runner scheduling.
+ Prefer removing proven duplicate preparation to deleting distinct assertions.
+ Preserve malformed input, cancellation, cleanup, identity, permission, capacity
+ and meaningful concurrency cases where relevant. Cached historical provider success
+ does not qualify a new runtime, permissions or engine contents.
+
+ If fixes are authorized, change the owning boundary and verify affected consumers
+ and meaningful negative cases. Do not suppress failures, blanket-retry, raise all
+ timeouts or prune checks solely to make CI green. Full suites are justified by
+ broad risk or unresolved discovery, not every documentation correction.
+
+ Return revision, scope, reproduction, observed/expected result, consequence,
+ recommended correction and check limitations for each finding. Distinguish local
+ runs from hosted current-head CI and main verification. Stop at the authorized
+ assessment/fix; publishing issues, merging or running native providers needs its
+ own scope. See the [worked example](references/worked-example.md) and
+ [source record](../reverse-engineer-anything/references/source-record.md).