Merge branch 'main' into dbaeumer/ts7context

Author: dbaeumer

.eslint-allowed-javascript-files

@@ -16,6 +16,13 @@ build/builtin/browser-main.js
 build/builtin/main.js
 build/npm/stubs/sharp/index.js
 build/codex/generate-protocol.mjs
+build/next/devTunnelsWebEntry.js
+build/next/devTunnelsShims/buffer.js
+build/next/devTunnelsShims/bufferutil.cjs
+build/next/devTunnelsShims/empty.cjs
+build/next/devTunnelsShims/process.js
+build/next/devTunnelsShims/utf8Validate.cjs
+build/next/devTunnelsShims/vscodeJsonrpc.cjs
 eslint.config.js
 extensions/copilot/.mocha-multi-reporters.js
 extensions/copilot/.mocharc.js

.github/CODEOWNERS

@@ -18,3 +18,12 @@ src/vs/workbench/services/extensions/common/extensionPoints.json @TylerLeonhardt
 # Adding entries here lets a new .js/.cjs/.mjs file land in the repo;
 # review is required to make sure TypeScript is not a better choice.
 .eslint-allowed-javascript-files @alexr00 @alexdima @sbatten @TylerLeonhardt
+
+# Agents Window architecture specifications and their routing policy.
+# These files describe stable contracts and should not change for routine fixes.
+/src/vs/sessions/*.md @sandy081
+/src/vs/sessions/contrib/layout/browser/*.md @sandy081
+/src/vs/sessions/contrib/providers/*/*.md @sandy081
+/.github/instructions/sessions.instructions.md @sandy081
+/.github/skills/sessions/SKILL.md @sandy081
+/.github/skills/chat-customizations-editor/SKILL.md @sandy081

.github/dependabot.yml

@@ -14,5 +14,7 @@ updates:
     directory: "/extensions/markdown-language-features"
     schedule:
       interval: "daily"
+      time: "16:00"
+      timezone: "America/Los_Angeles"
     allow:
       - dependency-name: "@vscode/markdown-editor"

.github/skills/agent-host-logs/SKILL.md

@@ -25,9 +25,12 @@ Files are collected best-effort, so a valid bundle may contain only some of thes
 events.jsonl
 usage.jsonl
 customizations.json
-Agent Host.log
-Window.log
-Shared.log
+agenthost.log
+agenthost.1.log
+agenthost-server.log
+vscode-logs/Window/renderer.log
+vscode-logs/Window/renderer.1.log
+vscode-logs/Shared/sharedprocess.log
 ahp/*.jsonl
 copilot-logs/*.log
 remote-agenthost.log
@@ -47,10 +50,10 @@ Window/client <-> AHP <-> Agent Host process <-> Copilot SDK
 | `usage.jsonl` | Client-captured token/credit usage, one record per model call (`turnId`, model, input/output/cache tokens, cumulative `totalNanoAiu`). The SDK's `assistant.usage` event is ephemeral and never reaches `events.jsonl`, so this is the only per-call usage record. Present only when agent-host debug logging was on. |
 | `customizations.json` | Snapshot of the skills/hooks/agents/MCP servers loaded for the session. The SDK's `session.*_loaded` events are ephemeral, so this is the only record of what was actually active. Present only when agent-host debug logging was on. |
 | `ahp/*.jsonl` | AHP traffic for a client connection. `_ahpLog.dir` is `c2s` or `s2c`; `_ahpLog.ts` is the wire timestamp. Use this to see requests, responses, subscriptions, actions, notifications, and client-visible ordering. |
-| `Agent Host.log` | Local Agent Host process behavior: startup, auth, sessions, provider events, tools, Git/worktrees, and host-side errors. |
+| `agenthost*.log` | Local or server Agent Host process behavior: startup, auth, sessions, provider events, tools, Git/worktrees, and host-side errors. Numbered files are older rotated segments. |
 | `copilot-logs/*.log` | Copilot SDK process logs that mention the selected session ID. A process log may contain other sessions too. |
-| `Window.log` | Renderer/client behavior: connections, session adapters, UI state, permissions, rendering, and client-side errors. |
-| `Shared.log` | Shared-process activity. Usually secondary evidence and often noisy. |
+| `vscode-logs/Window/*` | Current and rotated files from the Window log group, including renderer/client behavior, network activity, views, and other window-owned logs. |
+| `vscode-logs/Shared/*` | Current and rotated files from the Shared log group. Usually secondary evidence and often noisy. |
 | `Agent Host (<name>).log` | Forwarded logs from a named remote Agent Host. |
 | `remote-agenthost.log` | A directly downloaded remote `agenthost.log`, when available. |
 
@@ -62,9 +65,9 @@ Window/client <-> AHP <-> Agent Host process <-> Copilot SDK
    - Turn or provider behavior: `events.jsonl`
    - Token/credit usage or cost questions: `usage.jsonl`
    - Client/server state or ordering: `ahp/*.jsonl`
-   - Host implementation failure: `Agent Host.log`
+   - Host implementation failure: `agenthost*.log`
    - SDK behavior: `copilot-logs/*.log`
-   - UI behavior: `Window.log`
+   - UI behavior: `vscode-logs/Window/renderer.log` and its rotated segments
 4. Search by the known time or ID, then follow the same operation into the adjacent layer.
 
 Useful correlation fields include the raw session ID, session/chat URI, `turnId`, `interactionId`, tool/request IDs, JSON-RPC request `id`, AHP `serverSeq`, and event `id`/`parentId`.

.github/skills/chat-customizations-editor/SKILL.md

@@ -11,13 +11,15 @@ Split-view management pane for AI customization items across workspace, user, ex
 
 ## Spec
 
-**`src/vs/sessions/AI_CUSTOMIZATIONS.md`** — always read before making changes, always update after.
+**`src/vs/sessions/AI_CUSTOMIZATIONS.md`** — read for ownership and interface
+contracts. Update it only when those contracts change; behavior and regressions
+belong in focused tests.
 
 ## Key Folders
 
 | Folder | What |
 |--------|------|
-| `src/vs/workbench/contrib/chat/common/` | `ICustomizationHarnessService`, `ISectionOverride`, `IStorageSourceFilter` — shared interfaces and filter helpers |
+| `src/vs/workbench/contrib/chat/common/` | `ICustomizationHarnessService`, `ISectionOverride`, `ICustomizationItemProvider` — shared interfaces |
 | `src/vs/workbench/contrib/chat/browser/aiCustomization/` | Management editor, list widgets (prompts, MCP, plugins), harness service registration |
 | `src/vs/sessions/contrib/chat/browser/` | Sessions-window overrides (harness service, workspace service) |
 | `src/vs/sessions/contrib/sessions/browser/` | Sessions tree view counts and toolbar |
@@ -26,26 +28,25 @@ When changing harness descriptor interfaces or factory functions, verify both co
 
 ## Key Interfaces
 
-- **`IHarnessDescriptor`** — drives all UI behavior declaratively (hidden sections, button overrides, file filters, agent gating). See spec for full field reference.
+- **`IHarnessDescriptor`** — drives harness behavior declaratively (hidden sections, button overrides, item providers, agent gating). See spec for the stable ownership contract.
 - **`ISectionOverride`** — per-section button customization (command invocation, root file creation, type labels, file extensions).
-- **`IStorageSourceFilter`** — controls which storage sources and user roots are visible per harness/type.
-- **`IExternalCustomizationItemProvider`** / **`IExternalCustomizationItem`** — internal interfaces (in `customizationHarnessService.ts`) for extension-contributed providers that supply items directly. These mirror the proposed extension API types.
+- **`ICustomizationItemProvider`** / **`ICustomizationItem`** — internal interfaces (in `customizationHarnessService.ts`) for extension-contributed providers that supply items directly. These mirror the proposed extension API types.
 
 Principle: the UI widgets read everything from the descriptor — no harness-specific conditionals in widget code.
 
 ## Extension API (`chatSessionCustomizationProvider`)
 
-The proposed API in `src/vscode-dts/vscode.proposed.chatSessionCustomizationProvider.d.ts` lets extensions register customization providers. Changes to `IExternalCustomizationItem` or `IExternalCustomizationItemProvider` must be kept in sync across the full chain:
+The proposed API in `src/vscode-dts/vscode.proposed.chatSessionCustomizationProvider.d.ts` lets extensions register customization providers. Changes to `ICustomizationItem` or `ICustomizationItemProvider` must be kept in sync across the full chain:
 
 | Layer | File | Type |
 |-------|------|------|
 | Extension API | `vscode.proposed.chatSessionCustomizationProvider.d.ts` | `ChatSessionCustomizationItem` |
 | IPC DTO | `extHost.protocol.ts` | `IChatSessionCustomizationItemDto` |
 | ExtHost mapping | `extHostChatAgents2.ts` | `$provideChatSessionCustomizations()` |
 | MainThread mapping | `mainThreadChatAgents2.ts` | `provideChatSessionCustomizations` callback |
-| Internal interface | `customizationHarnessService.ts` | `IExternalCustomizationItem` |
+| Internal interface | `customizationHarnessService.ts` | `ICustomizationItem` |
 
-When adding fields to `IExternalCustomizationItem`, update all five layers. The proposed API `.d.ts` is additive-only (new optional fields are backward-compatible and do not require a version bump).
+When adding fields to `ICustomizationItem`, update all five layers. The proposed API `.d.ts` is additive-only (new optional fields are backward-compatible and do not require a version bump).
 
 ## Testing
 

.github/skills/sessions/SKILL.md

@@ -72,9 +72,26 @@ that preserve these boundaries:
 - Shared workbench changes represent shared capability, not Sessions-specific
   policy.
 
-Update a specification when its architecture or durable behavior changes. Do not
-add implementation chronology, rejected approaches, or bug narratives to a
-specification.
+### Specification edit gate
+
+Bug fixes do not update specifications when they restore an existing contract.
+Before editing an authoritative specification, identify all three:
+
+1. the existing ownership, interface, lifecycle, state-machine, persistence, or
+   cross-component contract that intentionally changes;
+2. the implementation surfaces affected by that contract change;
+3. why a regression test and a brief code comment cannot fully represent it.
+
+If any answer is missing, leave the specification unchanged. Put concrete
+behavior in a focused test, keep a non-obvious implementation constraint beside
+the owning code, and preserve investigation history in the issue or pull
+request.
+
+Update a specification only when component ownership, an interface or lifecycle
+contract, a state machine, persistence, or a cross-component invariant changes.
+Do not update specifications for styling, copy, action placement, telemetry
+fields, settings defaults, implementation algorithms, or individual bug fixes.
+Those details belong in code and focused tests.
 
 ## 5. Validate proportionally