@cratis/pi 7.107.0 → 7.108.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -22,17 +22,35 @@ before an external effect. A request to verify does not authorize a push.
|
|
|
22
22
|
1. Read `.github/workflows/` and the repository's tier policy. Follow reusable
|
|
23
23
|
workflows and invoked scripts. Extract commands, solution and test selection,
|
|
24
24
|
configuration, warning settings, analyzers, lint and formatting checks.
|
|
25
|
-
2.
|
|
25
|
+
2. Require an executable, repository-specific specification-project coverage
|
|
26
|
+
gate in CI; add one if absent and run its documented command locally where
|
|
27
|
+
inputs are available. Discover every spec project independently of CI's test
|
|
28
|
+
selection, then compare discovery with actual CI test commands and results.
|
|
29
|
+
Every project must run in some CI test job or be removed; a green subset,
|
|
30
|
+
a build-only job or solution membership is not execution coverage.
|
|
31
|
+
Follow reusable workflows and scripts, expand matrices and evaluate job/step
|
|
32
|
+
conditions for the relevant event and head SHA. Resolve project selection and
|
|
33
|
+
test filters; a command whose filters exclude all of a project's specs does
|
|
34
|
+
not cover it. A skipped conditional job cannot cover its assigned projects.
|
|
35
|
+
Keep command/filter mapping separate from runtime proof: correlate per-project
|
|
36
|
+
test results with the executed jobs for that SHA and require nonzero executed
|
|
37
|
+
specs per project. A static mapping alone cannot prove the tests ran.
|
|
38
|
+
Fail closed on empty or unknown discovery, unresolved selection/conditions,
|
|
39
|
+
missing results or uncovered projects. Print omitted project paths and the
|
|
40
|
+
missing/excluding job, command or filter so omissions are actionable. Pass only
|
|
41
|
+
when every discovered project has execution coverage; use repository tooling,
|
|
42
|
+
not a universal framework-specific scanner in this corpus.
|
|
43
|
+
3. Prefer the repository's existing gate script. If none exists, keep a small
|
|
26
44
|
local runner under `.ai-work/`, with each phase's real exit status preserved.
|
|
27
45
|
Do not substitute only the touched projects for the final gate.
|
|
28
|
-
|
|
46
|
+
4. **Tier 1** is the whole-solution build with CI's configuration and warning
|
|
29
47
|
settings, lint/format, and every non-integration test project. For example,
|
|
30
48
|
use Release with warnings as errors when that is what CI uses.
|
|
31
|
-
|
|
49
|
+
5. **Tier 2** adds integration tests. The repository's tier policy decides
|
|
32
50
|
whether they run locally. The default is CI-backed integration only if CI
|
|
33
51
|
runs that coverage, it passes before merge, and reviewer notes say it was
|
|
34
52
|
deferred to CI. If CI lacks that coverage, do not claim it is verified.
|
|
35
|
-
|
|
53
|
+
6. Name anything CI runs that cannot run locally: services, platforms, secrets
|
|
36
54
|
or hosted checks. Say what ran instead and what remains unverified before
|
|
37
55
|
pushing. Missing coverage is not a local pass.
|
|
38
56
|
|