docs: start milestone v1.1 Session Lifecycle, Memory & Reporting

.planning/PROJECT.md

@@ -27,7 +27,12 @@ The agent must NEVER mutate real infrastructure beyond what the limited IAM role
 
 ### Active
 
-(Next milestone goals to be defined)
+- [ ] **REPO-01**: Every new Hermes session auto-clones DEFAULT_REPOS (rai-ops, rai-deployment, rai-devtools)
+- [ ] **REPO-02**: User can request additional repos to clone on demand during a session
+- [ ] **MEM-05**: Long-term memory upgraded to hindsight (persistent cross-session recall)
+- [ ] **CRON-01**: Daily report summarizing active sessions sent via Telegram gateway
+- [ ] **CRON-02**: Stale sessions (inactive >30d) auto-archived with history preserved
+- [ ] **CRON-03**: Daily report updates Jira with session progress
 
 ### Out of Scope
 
@@ -67,6 +72,18 @@ The agent must NEVER mutate real infrastructure beyond what the limited IAM role
 - **Git**: Worktree-based isolation; pushes only to feature branches
 - **Gateway**: Telegram as primary messaging channel
 
+## Current Milestone: v1.1 Session Lifecycle, Memory & Reporting
+
+**Goal:** Productionize session workspace with default repos, upgrade to persistent cross-session memory (hindsight), and operationalize daily reporting with session lifecycle management.
+
+**Target features:**
+- Default repos auto-cloned into every new Hermes session
+- On-demand repo cloning during sessions
+- Hindsight long-term memory provider
+- Daily cron report (session summaries via Telegram)
+- Stale session auto-archive (30d)
+- Jira integration in daily reporting
+
 ## Key Decisions
 
 | Decision | Rationale | Outcome |
@@ -96,4 +113,4 @@ This document evolves at phase transitions and milestone boundaries.
 4. Update Context with current state
 
 ---
-*Last updated: 2026-06-14 after v1.0 milestone*
+*Last updated: 2026-06-14 — v1.0 shipped, v1.1 in planning*