syntaqxEnding a session by hand is a soft close: like one that timed out, it comes back the moment its harness is heard from again. An update or a recorded entry now brings it back, where before both were refused with 'This session has ended. Start a new one.' A start already did. So a harness that was still running picks up where it was, and one that is truly gone stays ended. A session its harness ended itself still stays ended. g1t_contracts::work::revives(end_reason) is the one rule, for timed_out and 'ended by hand by @…', and update, record and subagents' late hooks use it. The End session dialog and the sessions guide say so. Checked: cargo test -p g1t-contracts (322, new: what comes back when heard from), -p g1t-work (214), cargo check -p g1t-work (wasm32).de2b3aeHistory
- ..
- 0001_init.sql
- 0002_dependencies.sql
- 0003_repo_deleted.sql
- 0004_repo_archived.sql
- 0005_description_inherits.sql
- 0006_workspace_deleted.sql
- 0007_deploys.sql
- 0008_pins.sql
- 0009_activity.sql
- 0010_kind_and_links.sql
- 0011_drop_dependencies.sql
- 0012_production_image.sql
- 0013_reports_production.sql
- 0014_descriptions_are_projects.sql
- 0015_drop_repo_description.sql
- 0016_sweeps.sql