Commitb2816ec6Recorded2 Sep 2026Repositorysigil-web-styles
Strip the ci.sgv down to its steps
Message
Drops a ~40-line comment header and the explicit worker: timeout.
The timeout was redundant: with no worker: declared, host.sgl's effective-timeout falls back to the controller's host.default_timeout, which is the same 1800 the line was setting. Omitting it is better than declaring it, because the value now tracks controller config instead of being frozen into every repo. Verified: the compiled shell program is byte-identical either way.
The header's content belongs in the folio notes it was duplicating, not in fifteen copies. What remains is the same in every repo.
Changed
.kiln/ci.sgv | 39 ---------------------------------------
1 file changed, 39 deletions(-)Diff
.kiln/ci.sgvmodified
@@ -1,46 +1,7 @@
−1
;;; ci.sgv -- sigil-web-styles CI, defined natively in kiln's job language.−2
;;;−3
;;; No `.kiln/ci.sh`. The three steps below ARE the pipeline.−4
;;;−5
;;; `on:` IS MANDATORY AND ITS ABSENCE IS SILENT. A workflow with no `on:`−6
;;; matches no event, produces no error and no run, and still lints OK --−7
;;; so a missing `on:` reads exactly like a controller fault rather than−8
;;; like this file.−9
;;;−10
;;; NO `branch:` FILTER ON `push`, deliberately: a filter would narrow−11
;;; coverage to one ref. `(pull-request)` is not declared either -- kiln's−12
;;; matcher accepts it, but no run of that kind has been observed on this−13
;;; controller, and declaring coverage nobody has seen fire is how a green−14
;;; comes to mean less than it looks.−15
;;;−16
;;; ONE NODE, NOT THREE JOBS. Every node gets its own worker and its own−17
;;; delivered tree, and `sigil deps install` leaves a link farm in the−18
;;; workspace pointing at content under $HOME -- so splitting the stages−19
;;; across nodes means either shipping the whole of `build/` between them (138 MB−20
;;; measured on sigil-http) or depending on $HOME being shared between leases.−21
;;; Reasoning and measurements: topics/kiln-native-pipeline-single-node-template.−22
;;;−23
;;; STEP NAMES DO NOT FOLD IN THE UI TODAY, and that is a kiln bug, not a−24
;;; mistake here: `nodeexec.sgl` emits `##[kiln:section-start:<name>]` and−25
;;; the log viewer's parser wants the legacy `##[kiln:section-start <ms>−26
;;; <name>]`. Keep the names -- they are the contract any future−27
;;; comparison rests on -- but expect plain log lines until that is fixed.−28
;;; There is also no check ledger here: that whole contract lives in each−29
;;; repo's `.kiln/ci.sh`, and this pipeline has none.−30
;;; See topics/kiln-native-pipeline-emits-no-checks.−31
;;;−32
;;; `timeout: 1800` is CLAMPED by `safety.max_job_timeout` with no−33
;;; diagnostic -- a plain (min declared ceiling). 1800 is that key's−34
;;; default, so it survives on a controller that has not lowered it and is−35
;;; silently reduced on one that has. The effective value is printed once,−36
;;; in `Persistent worker ready ... timeout=N`, and only on the−37
;;; persistent-worker path.−38
1
(pipeline ci 2
on: #[ (push) (manual) ] 3
4
(job ci−43
worker: (worker timeout: 1800) 5
steps: #[ 6
(shell name: deps "sigil deps install") 7
(shell name: build "sigil build")