Skip to content

v0.62.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 04:51
· 139 commits to main since this release

v0.62.0 (2026-11-14)

Features

  • plan: A bolt is marked to stay by --stays when it is planned or started (bolt-plan; record 0067) (7c71fe7)
  • cards: A proposal's card says a bolt it marks to stay stays unlanded until the user's send (plan-proposals; record 0067) (68abf8a)
  • plan: Crew bolt unstay lifts a bolt's mark to stay, the user's or a proposal's (bolt-plan; record 0067, roles.2) (ddc4d77)
  • plan: A hold on a drive's or a kit's landings, put by crew plan hold and lifted by crew plan go (bolt-plan, main-level; record 0067) (6dce380)
  • plan: Lands_by says whether a landings row lands on proof, on the user's send or once a hold is lifted (rail-cards; record 0067, code.7) (8c5b652)
  • runner: A land on proof is due once for each head, a stop holding it only at the head it was posted at (rail-cards; record 0067) (1bd0fff)
  • plan: Each raise of a kit's landings card posts a land of each bolt due one on proof, after its sends' lands (rail-cards, run-record; plan.16, plan.8, record 0067) (2033ca0)
  • plan: A kit's landings card asks only about the rows a send must land (rail-cards; briefs.11, record 0067) (ce08962)
  • cards: A landings card tells the bolts landed on proof, as a one-tap notice where it asks nothing (rail-cards; briefs.11, record 0067) (9883f1c)
  • plan: Each bolt landed on proof is told on its kit's landings card until the user answers or taps a card that told it (rail-cards; briefs.11, record 0067) (5f6aa93)
  • plan: No land is posted while a hold stands on a kit or its drive, and the lift's raise posts what came due (rail-cards; record 0067) (30309e1)
  • rail: A bolt that can land says how it lands, and a kit's land row holds the bolts its card tells (crew-rail; record 0067) (9f8bb9a)
  • rail: The rail's read raises each kit with a bolt due a land on proof, and no read raises a card for one that lands on proof (rail-cards; plan.12, record 0067) (841fc74)
  • board: The planner's and ops's bands mark a bolt that stays and open with each hold standing (crew-board; code.8, record 0067) (582f186)

Fixes

  • plan: A proven bolt's landing holds to the verify's findings: Hold declared first, a stopped land on proof landed by the send, told lines drawn (cc99e24)
  • plan: A stopped land spends only the send that posted it, so a later card's send at its head lands the bolt and leaves the card answered (fc81e45)

Changes and specs

  • openspec: A-proven-bolt-lands-on-proof, a proven bolt lands on proof unless marked to stay, the card asks only what a send must land and tells the rest, and a hold on the drive or a kit stops both (plan.16, briefs.11, state.3; record 0067) (66b4424)
  • openspec: A-proven-bolt-lands-on-proof carries the verify's fixes as tasks 1.6 to 1.9, 2.8 to 2.11, 3.4, 3.5 and 4.5, all ticked (14a66c3)
  • openspec: A-proven-bolt-lands-on-proof carries a later card's send at a stopped land's head as task 2.12, ticked (b891711)
  • openspec: Archive a-proven-bolt-lands-on-proof, its specs synced: a proven bolt lands on proof, a bolt marked to stay on the user's send, and a hold stops both (471db16)

Documentation

  • briefs: Main-level ops's brief says a proven bolt not marked to stay lands on proof, the card asks only about bolts marked to stay, and a hold is the user's (briefs.11, plan.16; record 0067) (a4b8929)
  • briefs: The planner's brief says a bolt is marked to stay by --stays on the user's word, lifted by bolt unstay, and that it puts no hold (briefs.11; record 0067) (d14af6a)
  • readme: README, the crew skill and crew's usage say a proven bolt not marked to stay lands on proof, and name --stays, crew bolt unstay, crew plan hold and crew plan go (docs.2; record 0067) (9dc9f29)
  • plan: Lands_by and hold_rows say why a stop of any land holds a row for the send and why holds sit below a band's head line (3bbb115)
  • verify: A-proven-bolt-lands-on-proof is not archived: contract and t-journey-board fail on the Hold set coming last, and six scenarios fall short (fd8e017)
  • readme: README, the crew skill, crew's usage and ops's brief say a proven bolt lands on proof, or, marked to stay, on the user's send (26f69ad)
  • verify: A-proven-bolt-lands-on-proof is not archived: a later card's send at a stopped land's head is landed and then closed as spent (96874c8)
  • verify: A-proven-bolt-lands-on-proof holds: the whole checks pass, every task is ticked and every scenario is met (d1da57e)

Tests

  • help: Crew bolt unstay, crew plan hold and crew plan go answer their help and act on nothing (code.11) (3ba4fb3)
  • landings: The existing cases' bolts are marked to stay, so each case of the card's rows holds of rows it asks about (a77250d)
  • journey: The landing journey plans its bolts to stay and proves a bolt not marked landing on proof at the rail's read (rail-cards; record 0067) (a894816)