docs(template-contract): T4 aggregate must only allow skipped on fork PRs (mc#21) #37
Reference in New Issue
Block a user
Delete Branch "fix/t4-aggregate-fork-guard-guidance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs molecule-ci#21.
Documents the fail-closed T4 aggregator pattern for workspace templates that inline a live
t4-conformancegate. The guidance now explicitly states thatskippedis only acceptable on fork PRs; internal PRs and main pushes must seesuccess.This closes the shared-guidance half of #21; the per-template fixes are in:
APPROVED
6f2c544a. 5-axis clean: correctness documents the fork-PR-only skipped allowance for live t4-conformance aggregation and matches the fixed template pattern; robustness explicitly fail-closes internal PRs/main pushes when T4 is not success; security preserves host-root/token verification as a live hard gate; performance docs-only, no runtime path; readability guidance and bash snippet are clear.5-axis docs review on head
6f2c544a: correctness/robustness/security/performance/readability checked. Diff is docs-only in docs/template-contract.md and accurately documents the enforced live t4-conformance aggregate semantics: success required for push/internal PRs; skipped allowed only when github.event_name is pull_request and github.event.pull_request.head.repo.fork == true. No policy drift found; CI 4/4 green.