[pull] main from microsoft:main

build/lib/policies/policyData.jsonc

@@ -556,7 +556,7 @@
                 }
             },
             "type": "boolean",
-            "default": false,
+            "default": true,
             "included": true
         },
         {

extensions/copilot/assets/prompts/chronicle-standup.prompt.md

@@ -2,6 +2,6 @@
 name: chronicle:standup
 description: Generate a standup report from recent chat sessions
 ---
-Generate a standup report from my recent coding sessions. Use the **chronicle** skill — it documents the `copilot_sessionStoreSql` tool and the Standup workflow (call with `action: "standup"` to pre-fetch the last 24h of sessions, turns, files, and refs).
+Generate a standup report from my recent coding sessions. Use the **chronicle** skill — it documents the `copilot_sessionStoreSql` tool, the session-store schema, and the Standup workflow for summarizing the last 24h of activity from `sessions`, `session_refs`, `turns`, and `session_files`.
 
-When you invoke `copilot_sessionStoreSql`, set `subcommand: "standup"`.
+When you invoke `copilot_sessionStoreSql`, set `subcommand: "standup"` on every call.

extensions/copilot/assets/prompts/skills/chronicle/SKILL.md

@@ -13,25 +13,41 @@ Sessions may be stored locally (SQLite) and optionally synced to the cloud for c
 
 ## Available Tool Actions
 
-The `copilot_sessionStoreSql` tool supports three actions:
+The `copilot_sessionStoreSql` tool supports two actions:
 
 | Action | Purpose | `query` param |
 |--------|---------|---------------|
-| `standup` | Pre-fetch last 24h sessions, turns, files, refs | Not needed |
 | `query` | Execute a read-only SQL query | Required |
 | `reindex` | Rebuild local session index + cloud sync | Not needed |
 
 ## Workflows
 
 ### Standup
 
-When the user asks for a standup, daily summary, or "what did I do":
+When the user asks for a standup, daily summary, or "what did I do" (e.g. `/chronicle standup`):
 
-1. Call `copilot_sessionStoreSql` with `action: "standup"` and `description: "Generate standup"`.
-2. The tool returns pre-fetched session data (sessions, turns, files, refs from the last 24 hours).
-3. If the result is empty, tell the user no sessions were found in the last 24h, suggest `/chronicle reindex`, and stop — do not fabricate a standup.
-4. For any PR references in the data, check their current status (open, merged, draft) if possible.
-5. Format the returned data as a standup report grouped by work stream (branch/feature):
+**Step 1: Gather the last 24h of activity**
+
+Use `copilot_sessionStoreSql` with `action: "query"` and follow the SQL dialect shown in the tool description (SQLite locally, DuckDB on cloud — see the **Database Schema** and **Query Guidelines** sections below).
+
+Query the `sessions` table for rows where `updated_at` falls within the last 24 hours, ordered by `updated_at` descending. Recent-window predicate by backend:
+
+- **Local SQLite**: `WHERE updated_at >= datetime('now', '-1 day')`
+- **Cloud DuckDB**: `WHERE updated_at >= now() - INTERVAL '1 day'`
+
+Then, for those session ids, pull related references from `session_refs` (PRs, issues, commits). If you need more detail on a particular session, query `turns` (and `session_files`, or `checkpoints` on cloud) further — don't dump every turn for every session up front.
+
+If no sessions are found in the last 24 hours, tell the user there's no recent activity to report, suggest a longer window or `/chronicle reindex`, and stop. Do not fabricate a standup.
+
+**Step 2: Include PR-less work**
+
+Treat every recent session as a candidate work item, even when it has no PR, issue, or commit reference. PRs are supporting evidence, not the source of truth. Do not omit a session or branch solely because it has no PR — use session summaries and turn content to decide what to include.
+
+**Step 3: Check PR status and format**
+
+For any PR references found, use the GitHub CLI or MCP tools to check current status (open, merged, draft, closed). For each work item, include either a PR status line or a "No PR found" line — never invent a PR.
+
+Format the result grouped by work stream (branch/feature). Use exactly this structure:
 
 ```
 Standup for <date>:
@@ -41,26 +57,27 @@ Standup for <date>:
 **Feature name** (`branch-name` branch, `repo-name`)
   - 3-7 words describing the status
   - Key files: 2-3 most important files changed
-  - Merged: [#123](link)
-  - Session: `session-id`
+  - Merged: [#123](https://github.com/owner/repo/pull/123) or No PR found
+  - Session: `full-session-id`
 
 **🚧 In Progress**
 
 **Feature name** (`branch-name` branch, `repo-name`)
   - 3-7 words describing the current state of work
   - Key files: 2-3 most important files being worked on
-  - Draft: [#789](link)
-  - Session: `session-id`
+  - Draft: [#789](https://github.com/owner/repo/pull/789) or No PR found
+  - Session: `full-session-id`
 ```
 
 Rules:
 - Keep it concise and succinct — the user can always ask follow-up questions
 - Use turn data (user messages AND assistant responses) to understand WHAT was done
-- Use file paths to identify which components/areas were affected
+- Use file paths from `session_files` to identify which components/areas were affected
 - Group related sessions on the same branch into one entry
 - For sessions, only show the most recent session per feature/branch
 - Link PRs and issues using markdown link syntax
 - Classify as Done if work appears complete, In Progress otherwise
+- If a session has no branch or repo, include it under an "Other" section
 
 ### Tips
 

extensions/copilot/package.json

@@ -1236,7 +1236,7 @@
         "toolReferenceName": "sessionStoreSql",
         "when": "github.copilot.sessionSearch.enabled",
         "userDescription": "Query your Copilot session history using SQL",
-        "modelDescription": "Query the local session store containing history from past coding sessions. Uses SQLite syntax (NOT DuckDB or Postgres). SQL queries are read-only — only SELECT and WITH are allowed. Use `datetime('now', '-1 day')` for date math (NOT `now() - INTERVAL '1 day'`), FTS5 `MATCH` for text search.\n\nTables: `sessions`, `turns`, `session_files`, `session_refs`, `checkpoints`, `search_index`. For column details and query patterns, use the **chronicle** skill.\n\nActions: 'query' (execute SQL — supports JOINs, FTS5 MATCH, aggregations), 'standup' (pre-fetch last 24h data), 'reindex' (rebuild index from debug logs).",
+        "modelDescription": "Query the local session store containing history from past coding sessions. Uses SQLite syntax (NOT DuckDB or Postgres). SQL queries are read-only — only SELECT and WITH are allowed. Use `datetime('now', '-1 day')` for date math (NOT `now() - INTERVAL '1 day'`), FTS5 `MATCH` for text search.\n\nTables: `sessions`, `turns`, `session_files`, `session_refs`, `checkpoints`, `search_index`. For column details and query patterns, use the **chronicle** skill.\n\nActions: 'query' (execute SQL — supports JOINs, FTS5 MATCH, aggregations), 'reindex' (rebuild index from debug logs).",
         "tags": [],
         "canBeReferencedInPrompt": false,
         "inputSchema": {
@@ -1246,10 +1246,9 @@
               "type": "string",
               "enum": [
                 "query",
-                "standup",
                 "reindex"
               ],
-              "description": "The action to perform. 'query' (default) executes a SQL query. 'standup' pre-fetches last 24h session data for standup reports. 'reindex' rebuilds the local session index and syncs to cloud if enabled."
+              "description": "The action to perform. 'query' (default) executes a SQL query. 'reindex' rebuilds the local session index and syncs to cloud if enabled."
             },
             "query": {
               "type": "string",