[coverage] replaces [qa]: the coverage extension declares a package's floor, epsilon and required, a package with tests and no floor is judged at 100, and new projects list coverage by @willemkokke
The docs extension declares a docs phase and a deploy phase, and the task reference, the package generators and coverage's pages become their steps by @willemkokke
Every package lists its extensions, a contract's kind refuses naming the list to write, and the kind fallbacks, the backend protocol and the kind guards go by @willemkokke
Fm ci.dispatch follows the run it started: the run the forge names, or the one new dispatched run of its ref and commit, and two such runs refuse naming both by @willemkokke
Fm submit --every-runner labels a pull request ci:every-runner so the gate runs every runner for it, the forge adds labels to a pull request on every backend and refuses an unknown one by name, the gate workflow runs on labeled and its legs job picks the full matrix while the label is there, the repository configuration creates the label, and the coverage union expects every leg from a labelled pull request by @willemkokke
The Gitea adapter reads an epoch timestamp as a time the server has not set, and a job still running when the gate job collects is measured to the collection and named incomplete by @willemkokke
Credentials in command lines reach a profile trace as *, and a test's mounts and environment writes are undone before the next test by @willemkokke
This repository's packages list their extensions by @willemkokke
Remove what the redesigns left behind: the register-and-withdraw functions, dead definitions, leftover sweeps, empty stylesheets and the text naming kinds and seeds by @willemkokke
Forge lookups ask each backend's narrowest query and stop reading once they have what they need: pull requests by branch and commit, runs by workflow and limit, tags by prefix by @willemkokke
The descendant chain passes again: it drives the dev containers with the credentials their seed recorded and takes this checkout's code from the checkout index by @willemkokke
The abort reconcile spawns the runner by its real module, two footman invariant tests scan the real tree again, the push guard tests the branch a push names, and the review's smaller faults go by @willemkokke
Footman's internal modules are private, every public module under a root is its api or declared there, and other packages' sources reach footman through its api by @willemkokke
Every forge refuses a missing credential in one shape, GitLab falls back to glab, and the lane names its own variables by @willemkokke
A package's docs section is the package's, and the site assembles its config at build time by @willemkokke
The watch prints every job's move as it happens, stamped with the elapsed time, and names a red job with its failure lines at once by @willemkokke
A forge release takes assets: upload_asset and assets on the protocol, on GitHub, Gitea, GitLab and the fake by @willemkokke
A conan member's caches ride its own release, and every declared floor is built against by @willemkokke
The commit a merge made, and a gate that skips a deleted test by @willemkokke
The layering lint reads what the sources use, and each kind answers for its own by @willemkokke
A managed file carries the regions the repository owns by @willemkokke
The conformance loop's cpp-conan member, its runner on Debian, and the fixes the pass found by @willemkokke
Every workshop.toml key is declared by the layer that reads it, and a contract holds nothing else: an unknown key, an unlisted layer's key, a wrong type or value refuses on read by @willemkokke
Every distribution root is a namespace whose public names live in its api module, and the docs layer moves to livery.extensions.docs by @willemkokke
Extensions replace layers: each declares itself in the workshop.extensions entry point group, and a workspace lists them by name in [workspace] extensions by @willemkokke
Plugins mount through the project builtin rung: the workshop mounts the listed extensions from its own entry module, and the rendered tasks.py keeps only its comment by @willemkokke
A tool requirement takes ? and !: an optional tool is locked where it can be served and never refused, and a plugin declares the tools its verbs need by @willemkokke
Footman scans the installed entry points once per process and shares the scan through installed_entry_points, and a plugin declares its tools in a data module by @willemkokke
The copier answers move into workshop.toml: identity in [workspace], members from discovery with their own description, dev-extras and template, and the answers files go by @willemkokke
Tasks.py and each package's cliff.toml are composed by the fragment engine, so copier only births by @willemkokke
The contract key type becomes kind by @willemkokke
A verb that reaches no forge and no tool store loads neither: the forge, store and strongroom roots serve their names on first use, and the workshop and the bench import the store where they use it by @willemkokke
The state store reads and writes a series in a fixed handful of git processes by @willemkokke
A given body updates a reused pull request by @willemkokke
Livery.toolroom is a namespace, the handles live in livery.toolroom.tools by @willemkokke
The merged head decides what a merge left behind, and the release act cleans up after itself by @willemkokke
The loop's verbs at the top level: start, commit, abandon a branch, submit --no-close, and issue.reopen by @willemkokke
Tests are namespaced by their path, and a helper carries its package's name by @willemkokke
The gate runs on command, and a GitLab pipeline names its workflow by @willemkokke
One renderer per forge for the gate, the merge and the nightly, and the clock on GitLab by @willemkokke
Every GitLab pipeline names its workflow, a merge request pipeline is a pull request run, and the recorder's pytest is a child by @willemkokke
The GitLab lane is born: fm ci.e2e --forge=gitlab merges the setup PR on the real runner and proves the verified skip by @willemkokke
The GitLab runner carries the toolchain, the docker socket is opt-in on both lanes, and the members and the three legs prove themselves on merge request pipelines by @willemkokke
The release act, the points by hand and the clock on GitLab: the loop is whole on both lanes by @willemkokke
Issue.show prints one issue whole, and the protocol reads an issue's thread by @willemkokke
Forge.conformance runs the suites in replay or live against the local forges, the cassettes untouched by @willemkokke
The protocol, frozen: all three backends and the verified fake pass
the one conformance suite, so the drafts below are the contract.
The protocol: Forge, Repository (with the pr, checks,
issue, and release groups), and Registry, with the value types
they speak and ForgeError carrying the server's own words.
cancel_run(run, *, force=False) is required everywhere, force
being the first capability probe.
GitlabForge: the GitLab backend (REST v4, stdlib only), the odd
one out made real: iids never leak, pipelines are the checks
answer, force_cancel and required_contexts are declined by
name, and the asynchronous behaviours the container taught are
absorbed at the boundary (see the package's quirks list).
ci_secrets joins the capabilities. Gitea and GitLab support it
outright; on GitHub it rides the github-secrets extra (PyNaCl for
the sealed-box encryption the secrets API demands), loaded lazily,
with supports("ci_secrets") answering for the running install.
GithubForge: the GitHub backend (REST plus the GraphQL auto-merge
pair), token resolution GITHUB_TOKEN then gh auth token.
GiteaForge: the Gitea backend (REST v1, stdlib only), with the
1.28 server floor probed at cancel_run and the one-host token
rule (gitea_is_configured_host).
livery.forge.testing: the verified FakeForge with deterministic
fault injection (Faults), the conformance suite (SCENARIOS over
a per-backend ForgeDriver), and the HTTP record and replay layer
(Cassette, RecordingOpener, ReplayOpener) with secrets
scrubbed at record time. The conformance driver states each push's
CI outcome at push time (Outcome), which is what a real forge can
actually be made to do.
Unsupported: the exception a backend raises when the server
predates an operation or a capability is declined by name.
Package skeleton: the livery.forge PEP 420 namespace module, the
package contract (livery.toml), and the stdlib-only runtime rule
under test. Reserves the distribution name and proves the release
train end to end.