compact: default the range to what has settled #130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/task/santi-compact-default"
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?
compact: default the range to what has settled
Compacting required naming both boundaries, so the cheapest way out of
context pressure was always to accumulate a little longer rather than to
curate. That is the wrong gradient to leave in place before a ceiling
starts refusing work: if the least effortful escape from a block is to
keep every turn small, what gets learned is avoidance.
With no range given, collapse everything settled since the last occupied
slot. The floor is the far end of the furthest slot no other slot covers,
so repeated defaults walk forward instead of recompacting what is already
compacted, and the most recent message is always left out, because a
default that swallowed the live exchange would take with it the very
request being acted on.
When nothing has settled, say so and name the sequence the floor sits at,
rather than refusing for the reason that no boundaries were given.
The command line takes the range as an optional pair, so the default is
reachable from the only tool a soul has. Its help and the public schema
move, so both contract digests move. The CLI digest was checked against
an unchanged build in the same cleared environment first: this test also
renders whatever SANTI_ variables the calling shell holds, so a drifting
digest is not by itself evidence that the contract changed. Here it did.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com