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
- ..
- accounts.rs
- allocate_usage.sql
- allocation.rs
- budget.rs
- cards.rs
- charged.rs
- closing.rs
- complimentary.rs
- compute.rs
- costs.rs
- credits.rs
- cycle.rs
- detach.rs
- details.rs
- enterprise_attempt.rs
- features.rs
- grants.rs
- invoice_attempt.rs
- invoices.rs
- keeper.rs
- lib.rs
- limits.rs
- margin.rs
- overages.rs
- platform.rs
- pricing.rs
- refund_extras.sql
- refund_ledger.sql
- refund_plan.sql
- rename.rs
- report.rs
- requests.rs
- reset.rs
- retention.rs
- sales.rs
- statement.rs
- storage.rs
- stripe.rs
- stripe_sync.rs
- subscriptions.rs
- tax.rs
- webhooks.rs