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_text_ids.sql
- 0003_unique_email.sql
- 0004_email_verification.sql
- 0005_token_expiry.sql
- 0006_device_codes.sql
- 0007_rfc3339_timestamps.sql
- 0008_workspaces.sql
- 0009_oauth.sql
- 0010_workspace_tokens.sql
- 0011_agent_tokens.sql
- 0012_avatars.sql
- 0013_profiles.sql
- 0014_workspace_redirects.sql
- 0015_run_credentials.sql
- 0016_deleted_workspaces.sql
- 0017_github.sql
- 0018_invites.sql
- 0019_user_emails.sql
- 0020_access.sql
- 0021_waitlist_notices.sql
- 0022_token_scopes.sql
- 0023_retire_token_reach.sql
- 0024_g1t_name.sql
- 0025_workspace_soft_delete.sql
- 0026_workspace_residency.sql
- 0027_teams.sql
- 0028_team_creation.sql
- 0029_workspace_aliases.sql
- 0030_job_tokens.sql
- 0031_membership.sql
- 0032_two_factor.sql
- 0033_identity_jobs.sql
- 0034_fine_grained_tokens.sql
- 0035_deploy_keys.sql
- 0036_email_confirmation_codes.sql
- 0037_account_deletion.sql
- 0038_shared_invites.sql
- 0039_profile_timezone.sql
- 0040_workspace_invitations.sql
- 0041_one_kind_of_token.sql
- 0042_username_case.sql
- 0043_website_tokens.sql
- 0044_dock_pins.sql
- 0045_people_and_teams.sql
- 0046_sound_settings.sql
- 0047_suspension.sql
- 0048_ask_tokens.sql
- 0049_privacy.sql
- 0050_onboarding.sql