|
|
e10b4ad4f0
|
refactor: move scope authority to pod store
|
2026-05-30 07:36:17 +09:00 |
|
|
|
211738132c
|
refactor: split pod metadata store
|
2026-05-30 07:16:50 +09:00 |
|
|
|
20ac0c96a5
|
fix: remove generic overlay startup path
|
2026-05-30 04:34:27 +09:00 |
|
|
|
0b23aa8191
|
fix: rename installed binaries
|
2026-05-29 09:28:31 +09:00 |
|
|
|
d6fd4d1b9c
|
fix: confirm initial SpawnPod run delivery
|
2026-05-28 22:14:28 +09:00 |
|
|
|
3f260d7d4e
|
fix: confirm SpawnPod initial run delivery
|
2026-05-26 08:37:24 +09:00 |
|
|
|
fd1b06198e
|
feat: add visible pod discovery tools
|
2026-05-23 12:04:45 +09:00 |
|
|
|
a26f18c466
|
fix: reclaim delegated scope from stopped children
|
2026-05-23 08:38:42 +09:00 |
|
|
|
a267ad8114
|
feat: show context usage in tui status
|
2026-05-23 07:15:03 +09:00 |
|
|
|
767400d5c2
|
fix: drain snapshots before pod callbacks
|
2026-05-23 04:57:03 +09:00 |
|
|
|
4795b6cb4a
|
refactor: remove legacy plural log entries
|
2026-05-23 02:03:42 +09:00 |
|
|
|
1e0dc6566c
|
feat: persist spawned pod registry
|
2026-05-22 23:30:02 +09:00 |
|
|
|
c2b55a498b
|
update: 残存 Session 識別子の Segment 化（review follow-up）
レビュー指摘の通り、次の session-grouping-introduce で新 SessionId が
入る前に名称衝突を避けるため取り残しを掃除。
- PodError::Session{Empty,ScopeMissing} → Segment{Empty,ScopeMissing}
- ScopeLockError::SessionConflict → SegmentConflict
- Pod.session_state / SegmentState.set_session_id 系
- source_session_id / prev_session_id / ensure_session_head / short_session
- pod_cli の "Session ID:" 表示
- fs_store の sessions ローカル変数
|
2026-05-20 05:17:49 +09:00 |
|
|
|
22f5d02385
|
update: SessionId / SessionStart / SessionOrigin 等を Segment 系名称へ
- Type/Function/Variantを Segment* 系へ統一
- SessionId/SessionStart/SessionOrigin/SessionStartState/SessionState/SessionLogSink/SessionLockInfo
- new_session_id / session_id / create_session* / list_sessions / lookup_session / update_session / find_by_session
- protocol Event::SessionRotated → SegmentRotated、CompactDone.new_session_id → new_segment_id
- Module: session_log → segment_log / session → segment (file mv 含む)
pod 側の session_log_sink → segment_log_sink も同様
- crate 名 (session-store)、CLI flag (--session)、ResumeWithSession (CLI tied) は据え置き
- session-tests/session_metrics_test 等の Store impl も追従
|
2026-05-20 05:06:04 +09:00 |
|
|
|
e7064878c2
|
refactor: Podのメインループのリファクタリング
|
2026-05-14 03:27:49 +09:00 |
|
|
|
4e48f35e55
|
feat: resume時のscope claimを過去の有効scopeに揃える
|
2026-05-03 17:12:36 +09:00 |
|
|
|
d33b1c111e
|
feat: dynamic-scopeの実装
|
2026-05-02 01:26:17 +09:00 |
|
|
|
0b322a645a
|
pod-registry-rename修正
|
2026-04-29 21:04:47 +09:00 |
|
|
|
8a8fd225bf
|
scope-lock -> pod-registry
|
2026-04-29 20:01:32 +09:00 |
|
|
|
fd96a517bb
|
tuiからセッションを復帰する経路の実装
|
2026-04-29 19:03:03 +09:00 |
|
|
|
7a0ed7d744
|
cargo fmt
|
2026-04-27 22:51:07 +09:00 |
|
|
|
0a3af686f7
|
submitをvec segmentを受け付ける形に変更
|
2026-04-27 11:03:58 +09:00 |
|
|
|
2ee536ed71
|
Method::NotifyとEvent::Notificationが紛らわしい問題
|
2026-04-26 23:25:50 +09:00 |
|
|
|
4763173f36
|
podのモジュール分割
|
2026-04-24 11:48:27 +09:00 |
|
