Landed deterministic container publishing for clojnder:
CI now pushes SHA tags and release tags, Binder publish uses the
matching deterministic base-image tag, and BinderHub's
.binder/Dockerfile is pinned to an immutable GHCR digest
instead of :latest.
Diagnosed and fixed successive deploy/runtime failures: Binder
publish was using the full Git SHA instead of the short Docker metadata
SHA tag; the packaged JupyterLab extension had been built against newer
JupyterLab packages than Binder's 4.2.5 runtime; and Binder
preview routes were registered at absolute
/clay-preview/... paths instead of under Jupyter's per-user
base_url.
Rebuilt and repackaged the labextension with Binder-compatible
JupyterLab deps, added CI checks for labextension compatibility and
preview-route smoke coverage, and confirmed local Binder images report
clay-jupyter-proxy v0.1.0 enabled OK.
Closed and pushed beads work for deterministic image publishing /
Binder digest pinning / Binder route registration; current production
image debug trail ended with commit 9e243ff
(fix: register preview routes under jupyter base url).
Arc: moved from the earlier preview-panel
implementation into hardening the Binder deployment path end-to-end:
deterministic images, compatible frontend assets, and finally
Binder-prefixed backend route registration.
Next: launch a fresh Binder session built from
9e243ff or later and verify
/user/<session>/clay-preview/api/status and
/render resolve; if Binder debugging continues to be
painful, add explicit image/version metadata into the image for easy
in-pod inspection.
Session 21:11 (elegua)
Read ~/Downloads/elegua-features.md and converted its
numerical-validation roadmap into an OpenSpec proposal for Eleguá.
Created openspec/changes/add-numerical-validation-core/
with proposal.md, design.md,
tasks.md, and
specs/numerical-validation/spec.md covering numeric
comparison, capability negotiation, differential/convergence fixtures,
provenance/history, array blobs, adapter pooling, fixture ergonomics,
and diagnostics.
Validated the proposal with
openspec validate add-numerical-validation-core --strict.
Committed and pushed
a3bf9d2 spec: propose numerical validation core to
origin/main; pre-push tests passed
(459 passed, 1 skipped, 13 deselected).
Noted bd sync is unavailable in this repo's current
bd CLI, and unrelated working-tree changes remain outside
the committed proposal.
Next: review/approve the OpenSpec change, then
split implementation into TDD-sized beads before applying it; consider a
separate elegua-finance plugin proposal for domain-specific
finance features.