You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
6 contractiles fail nickel typecheck: import path points one level off an existing file #934
All 6 contractile definitions fail nickel typecheck on an unresolvable relative import. The imported file exists — it is simply at a different path than the import states, so this is a stale path to repair, not missing work.
Measured evidence
nickel-lang-cli nickel 1.17.0 (rev db7978e):
$ nickel typecheck .machine_readable/contractiles/must/must.k9.ncl
error: import of ../k9/template-hunt.k9.ncl failed: could not find import
(looked in [<repo>/.machine_readable/contractiles/must])
┌─ <repo>/.machine_readable/contractiles/must/must.k9.ncl:30:15
│
30 │ let base_k9 = import "../k9/template-hunt.k9.ncl" in
│ ----------------------------------- imported here
From .machine_readable/contractiles/must/, the written ../k9/... resolves to .machine_readable/contractiles/k9/, which does not exist. The path that reaches the real file is ../../svc/k9/template-hunt.k9.ncl.
Acceptance criteria
All 6 contractiles resolve their imports and nickel typecheck exits 0 for each.
The correction is verified by running typecheck, not by reading the path — confirm ../_base.ncl resolves too, since it sits on the same stale assumption.
If svc/ was a deliberate move, every other importer of k9/ is checked for the same breakage; state the count.
Activity
feat(ci): ratchet ci-pipeline adoption behind a shrink-only ledger (#948