Ci Verification
Pre-PR verification for webframp/swamp-extensions, as typed, versioned swamp data. Runs the checks CI runs against one commit, in a throwaway worktree at that commit, and records every result and its log keyed by the commit's tree hash. Builds an attestation from the recorded results and posts it as a git ref (refs/attestations//), never forced.
Quick Start
swamp extension pull @webframp/ci-verification
# Verify a commit of a swamp-extensions checkout. Each workflow step names
# the model type and the instance name ci-verification, so swamp creates
# that instance on the first run.
swamp workflow run @webframp/ci-verification-verify \
--input repoPath=/path/to/swamp-extensions \
--input commit=<sha> --input base=<base-sha>
# Build and post the attestation once reviews are done. A change to the
# trust root (ci-discover, check-reserved-names, this extension, CI
# workflows) needs an approval with decision "approve". To run methods
# before the workflow has run, create the instance first:
# swamp model create @webframp/ci-verification ci-verification
swamp model method run ci-verification attest \
--input repoPath=/path/to/swamp-extensions --input commit=<sha> \
--input 'approvals:json=[{"gateId":"release-approval","decision":"approve"}]'
swamp model method run ci-verification post \
--input repoPath=/path/to/swamp-extensions --input commit=<sha>Methods
- discover: which extensions the diff selects, from the repository's own scripts/ci-discover
- check: check, lint, fmt:check, test and manifest fmt per extension, plus the repo-wide checks CI runs
- quality: the registry quality rubric per extension
- attest: the attestation for a tree, from recorded results
- post: push the attestation as a git ref
Workflow
- @webframp/ci-verification-verify: discover, check and quality in sequence
2026.11.12.1
Added: Initial release. A model, @webframp/ci-verification, that runs the
checks swamp-extensions CI runs against one commit and records every result and
its log as swamp data, keyed by the commit's tree hash:
discoverrecords which extensions and repo-wide checks the diff selects, using the commit's ownscripts/ci-discover.checkruns each selected extension's check, lint, fmt:check, test and manifest fmt, plus the reserved data name scan, the import specifier greps and the tasks of each touchedscripts/tool.qualityrunsswamp extension qualityunder CI's pass condition.attestbuilds an attestation from the recorded results and refuses if any result is missing, failed, or stale, if a review failed or an approval's decision is notapprove, or if the change touches the trust root (ci-discover, check-reserved-names, this extension, CI workflows) and no approval with decisionapprovewas given.postpushes the attestation torefs/attestations/<tree>/<timestamp>, never forced.
Every method runs in a throwaway worktree at the commit, with an allowlisted environment for child processes. A rerun reuses passed results and reruns failed ones.
Added: The @webframp/ci-verification-verify workflow, which runs discover,
check and quality in sequence.
| Argument | Type | Description |
|---|---|---|
| base | string | The base the diff is taken against |
| Argument | Type | Description |
|---|---|---|
| reviews? | array | Review verdicts, recorded as asserted by the caller |
| approvals? | array | Approvals, recorded as asserted by the caller; when the change touches the trust root, one must have decision "approve" |
| Argument | Type | Description |
|---|---|---|
| remote? | string | The git remote to push the ref to |
Resources
Files
Verify a swamp-extensions commit before opening a pull request: discover which extensions the diff from base selects, then run each one's check, lint, fmt:check, test and manifest fmt with the repo-wide checks, then the registry quality rubric. Results and logs are stored as swamp data keyed by the commit's tree. Each job runs only when the one before it succeeded. The workflow never posts an attestation; run the model's attest and post methods when the change is ready to release.
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault1/1earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned