Commit sigil.lock; lockfiles are tracked in this estate

Message

This repo was not committing its resolution record -- blackice and core-channel gitignored it, sigil-doc simply never added it. Every other repo in the estate tracks sigil.lock, so these were the exceptions rather than a deliberate policy.

The concrete harm, found during the monorepo pin sweep: an untracked lock is INVISIBLE TO git diff, which reports it as no change. So a classifier asking "did this repo's lock move?" answered NO while the worktree lock had already been rewritten -- blackice's HEAD had zero >= refs and its worktree had five, and git diff still said clean. A file that is simultaneously changed and invisible defeats exactly the check meant to catch it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P6mPymR1ZBRV1nuyDpBxDF

Changed

 .gitignore | 1 -
 sigil.lock | 9 +++++++++
 2 files changed, 9 insertions(+), 1 deletion(-)

Diff

.gitignoremodified

@@ -6,4 +6,3 @@ toolchain/bin/

toolchain/zig-x86_64-linux-0.16.0/

toolchain/zig-x86_64-linux-0.16.0.tar.xz

.sigil/

−9

sigil.lock

sigil.lockadded

@@ -0,0 +1,9 @@

;; Auto-generated by sigil deps install. Do not edit.

(lock

(package name: "sigil-stdlib"

url: "codeberg:sigil/sigil"

ref: ">=0.20, <1.0"

sha: "2e452e2f641fcf63be4e88a2748b34791543be8f"

package-selector: "sigil-stdlib"

version: "0.20.3")

)