[REPPL]

A session told that a release cut holds the merges was never told when that hold stopped holding. A hold lapses when the cut stops renewing it, but nothing said so, so a session kept waiting on a hold that held nothing.

What changes:

• Every hold line names the time the hold lapses unless the cut renews it, and the waits that end on a hold name that time too.
• The prompt hook's status block shows each lapsed cut once, so a session that was told of a hold is told when it lapses.
• A lapse older than a week is not shown again, so a spent status branch waiting for the sweep is not re-announced every week.
• The lapsed cuts are read in the same read of the shared view as the holds, so the two cannot disagree.
• The CONCURRENCY rule, its short form in AGENTS.md, and the launch, peers, land, build, reserve and status pages say that a hold binds only until it lapses, needs no one's leave to set aside after that, and is re-read just before it is acted on or passed on.

Tests:

• the hold lines and waits name the lapse;
• a lapsed cut is shown once to a session that saw the hold, and not again;
• a session that first reads the block a week after the lapse is not shown it. A mutant run with the week filter turned off fails this test, and the branch passes it.

Resolves: iss-2610241107191205

Assisted-by: Claude:claude-opus-5-5