Commit Graph

14 Commits

Author SHA1 Message Date
c04b1ca289
fix: validate spawn delegation authority 2026-06-12 17:10:59 +09:00
9dcbd4c3e0
docs: reorganize developer documentation 2026-06-01 20:59:32 +09:00
e6c458021c
rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
d2e80871ce
fix: reconcile missing delegated children 2026-05-30 07:46:09 +09:00
a26f18c466 fix: reclaim delegated scope from stopped children 2026-05-23 08:38:42 +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
b90291d5a0 fix: resume-scope-claim レビュー指摘対応 (deny セマンティクス doc・破損 snapshot の警告ログ) 2026-05-03 18:56:21 +09:00
4e48f35e55 feat: resume時のscope claimを過去の有効scopeに揃える 2026-05-03 17:12:36 +09:00
99dc94416b chore: 依存パッケージの集約 2026-05-01 23:35:46 +09:00
bccd60d9be feat: memory P2の修正 2026-05-01 23:22:49 +09:00
f31c58dccd cargo fmt 2026-04-29 23:20:25 +09:00
274b7df32d pod-registryのモジュール分割 2026-04-29 20:14:34 +09:00
8a8fd225bf scope-lock -> pod-registry 2026-04-29 20:01:32 +09:00