Cold-start Posta and consume the wrapperless Runseal profile #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/posta-cold-start"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cold-start Posta as a library-first postal protocol
The working tree carried the whole cold start untracked: the posta crate,
its Keel-backed store, the L2 verification scenario, repository shape, and
operator wrappers. Only a three-line README was ever committed, and the
canonical remote PerishLab/posta does not exist, so this content had a
single copy on one disk.
Replay agreement is a named model. The store previously compared a held
letter to its replay inputs through two five- and six-parameter helpers,
each spreading seven Boolean atoms across one condition. Payload projects a
letter without its identity, and replayed compares that projection by
equality, so the complete semantic payload the protocol law names is one
value rather than an anonymous combination space.
Ectropy is clean. cargo fmt, clippy over the workspace with warnings
denied, the locked workspace tests, deno fmt, and the frozen deno check all
pass.
Three Plumb findings remain and block land, not this commit:
guard does not exercise the release profile [structure]
cargo keel resolves to 0.10.0, stable latest is 0.10.2
jsr @perish/sealkit resolves to 0.1.8, stable latest is 0.3.4
The Sealkit gap crosses two minors into a line that is still unsettled, and
the Keel floor is the co-evolution boundary AGENTS.md fixes at 0.10.0, so
neither moves as maintenance. The runseal.toml here also predates Runseal
v0.14.1, which cannot parse it, so the pre-commit hook could not run and
this commit bypassed it.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Consume the wrapperless Runseal profile
Runseal 0.14.1 refuses this repository's profile outright:
[resources],[deno], and[[injections]]are unknown fields, so everyrunsealinvocation failed at profile resolution and neither
runseal :guardnorrunseal :land— the two commands AGENTS.md names — could run. Local commitshad to bypass a pre-commit hook that could not execute either.
The profile is now the env-only shape: three
local://variables and nothingelse, matching Runseal itself and the four other repositories already migrated.
Generic wrappers and repository-owned hooks are not repository facts. The four
wrappers and two hooks are removed, and with them the whole
.runsealdirectory. Guard moves into its workflow, which now runs Plumb and Ectropy
directly rather than delegating to a wrapper, and gains the release-profile
type check the skeleton asks for. Landing belongs to
plumb land, which is whyno replacement for the land wrapper is introduced.
Sealkit leaves with the wrappers rather than by decision. It was declared in
.runseal/deno.jsonand imported by all four of them and by nothing undercrates/, so removing the wrappers removes the dependency and the stale0.1.8resolution it carried.The Keel requirement is untouched.
0.10.0is a caret requirement that alreadyadmits
0.10.2, so only the lock moved; the co-evolution floor this repositoryfixes at 0.10.0 is unchanged.
plumb doctor .is now true to the skeleton. The complete guard passes: doctor,fmt, clippy with warnings denied, a release-profile check, the locked workspace
tests, and Ectropy.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com