Renumber 6b-2 to 0.261.249

Keep all base version history; update only 6b-2's version, tests and documentation after the V2 #1641 merge.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: paullizer

application/single_app/config.py

@@ -101,7 +101,7 @@
 EXECUTOR_TYPE = 'thread'
 EXECUTOR_MAX_WORKERS = 30
 SESSION_TYPE = 'filesystem'
-VERSION = "0.261.239"
+VERSION = "0.261.249"
 IS_DEVELOPMENT = is_development_env_enabled()
 
 # Opt-out for deployments where App Service Easy Auth is active but the platform

docs/explanation/features/CHAT_ORCHESTRATION_WORKFLOW_RUNS.md

@@ -477,7 +477,7 @@ encoded as query values. It doesn't
 poll; the status is as of the read, and **Try again** reloads after a failed
 read. A 404 renders nothing.
 
-Since **0.261.239**, while `allow_user_workflows` and
+Since **0.261.249**, while `allow_user_workflows` and
 `enable_chat_orchestration_workflow_runs` are both on, Phase 6b-2's
 `WorkflowRunCard` shows the same runs from the same read, with their live status
 and **Check now**, **Cancel run** and **Retry**. These links are what shows when
@@ -599,7 +599,7 @@ See [Orchestration settings](../../admin/orchestration.md).
    as started, already started or not started with the reason.
 5. Under the answer, **Started workflows** shows each run's status. **Open run**
    opens the workflow in Workflows with its run history open at that run. Since
-   **0.261.239** the status stays current while the run is in flight; see
+   **0.261.249** the status stays current while the run is in flight; see
    [V2 experience (6b-2)](CHAT_WORKFLOW_RESULT_DELIVERY.md#v2-experience-6b-2).
 
 The user guide is
@@ -634,7 +634,7 @@ Ranking sorts the
 same bounded list proposals already read. A run step makes point reads of the
 conversation, the workflow and the run, and at most one queue call. The link
 route makes two point reads per started workflow, and none when the links are
-unavailable. The links don't poll. Live status since **0.261.239** comes from
+unavailable. The links don't poll. Live status since **0.261.249** comes from
 one tracker per browser tab and Phase 6b-1's batched status route, never a
 request per run.
 

docs/explanation/features/CHAT_WORKFLOW_RESULTS_FOLLOW_UP.md

@@ -736,7 +736,7 @@ the controls are listed in
 - Re-checking workflow result contexts when a generated file is published.
 - Phase 6b's delivery, run card, recurring-workflow card and chat-list
   indicator, and `v2WorkflowRunPath` shipped in 6b-1 (**0.261.227**) and 6b-2
-  (**0.261.239**). See
+  (**0.261.249**). See
   [Workflow result delivery to chat](CHAT_WORKFLOW_RESULT_DELIVERY.md), and
   [V2 experience (6b-2)](CHAT_WORKFLOW_RESULT_DELIVERY.md#v2-experience-6b-2)
   for **Follow up** on a posted result.

docs/explanation/features/CHAT_WORKFLOW_RESULT_DELIVERY.md

@@ -2,7 +2,7 @@
 
 Implemented in version: **0.261.227**.
 
-V2 experience (6b-2) implemented in version: **0.261.239**.
+V2 experience (6b-2) implemented in version: **0.261.249**.
 
 Application version tracking: `application\single_app\config.py`.
 
@@ -22,7 +22,7 @@ Workflows later to see what the run produced. With **Use Workflow Results In
 Chat** on, the server posts that run's terminal outcome back into the same
 private chat that asked for it, even if the run finishes hours later.
 
-The delivery is server-side. 6b-1 shipped no V2 run-card UI. 6b-2 (0.261.239)
+The delivery is server-side. 6b-1 shipped no V2 run-card UI. 6b-2 (0.261.249)
 polls the status route documented below and renders the run card, Retry and
 Open run; see [V2 experience (6b-2)](#v2-experience-6b-2).
 
@@ -311,7 +311,7 @@ Notice titles and messages are fixed:
 Undeliverable and expired notices link to
 `/workflow-activity?workflowId=...&runId=...&scope=personal` and carry metadata
 `{workflow_id, run_id, workflow_scope: 'personal', delivery_status}`. Since
-6b-2 (0.261.239), the V2 bell labels the type **Workflow results** and opens the
+6b-2 (0.261.249), the V2 bell labels the type **Workflow results** and opens the
 run on V2's Workflows page; see [Run links](#run-links).
 
 ### Message shape and placement
@@ -697,7 +697,7 @@ and route responses as the live truth.
 
 ## V2 experience (6b-2)
 
-Implemented in version: **0.261.239** (#1546 part 6b-2).
+Implemented in version: **0.261.249** (#1546 part 6b-2).
 
 6b-1 posts the result on the server. 6b-2 shows it in V2 while the user is
 working, so they don't have to open Workflows to find out whether the run they
@@ -1070,7 +1070,7 @@ All paths are under `application\v2_ui\src\` except `config.py`.
 | `lib\notificationLinks.ts` | `v2WorkflowRunPath` returns the run link, and workflow notices open their run in V2. |
 | `lib\workflowAlertNotices.ts` | A workflow alert's **Open run** uses the scoped run link. |
 | `lib\notifications.ts` | Labels `workflow_chat_delivery` notices **Workflow results** in the bell. |
-| `config.py` | Tracks version `0.261.239`. |
+| `config.py` | Tracks version `0.261.249`. |
 
 ## Usage
 
@@ -1227,7 +1227,7 @@ The implementation differs from the approved plan in these documented ways:
   `/workflow-activity?workflowId=...&runId=...&scope=personal` path.
 - The V2 bell showed the generic `Notification` label for
   `workflow_chat_delivery` until 6b-2 added the **Workflow results** case in
-  0.261.239.
+  0.261.249.
 
 ## Related
 

docs/explanation/features/V2_NOTIFICATIONS_BELL.md

@@ -167,7 +167,7 @@ leaves the open conversation alone.
 
 ### The seams for Phase 6b
 
-Phase 6b-2 (0.261.239) filled in all three; see
+Phase 6b-2 (0.261.249) filled in all three; see
 [Chat Workflow Result Delivery](CHAT_WORKFLOW_RESULT_DELIVERY.md) for the V2 side.
 
 - **Run pages.** `v2WorkflowRunPath(scope, workflowId, runId)` in

docs/explanation/features/V2_WORKFLOW_ALERT_NOTICES.md

@@ -19,7 +19,7 @@ Open and Dismiss up front, with everything else under Show more, since version:
 
 Hanging from the bell rather than **My Workspace** since version: **0.261.236** (#1642).
 
-**Open run** in Open workflow's place, for an alert that names its run, since version: **0.261.239**
+**Open run** in Open workflow's place, for an alert that names its run, since version: **0.261.249**
 (Phase 6b-2, #1546).
 
 Dependencies:
@@ -207,7 +207,7 @@ button under a dozen chips and links:
   lives in and opens the run that raised the alert:
   `/workspace/workflows?workflow_id=<id>&run_id=<id>`, or
   `/groups/<group id>/workflows?workflow_id=<id>&run_id=<id>` for a group workflow.
-  Until 0.261.239 this button was labeled **Open workflow**; the address is unchanged.
+  Until 0.261.249 this button was labeled **Open workflow**; the address is unchanged.
   It works when that list is already open, too. The workflows section acts on each
   navigation that names a workflow once, so choosing Open run again, even for
   the same run, opens the run again. Anything else that later changes the list, such
@@ -245,7 +245,7 @@ keyboard user doesn't lose their place.
 
 ### Hooks for later phases
 
-- **Open run** (filled in by Phase 6b-2, 0.261.239). `workflowAlertOpenRunPath` calls
+- **Open run** (filled in by Phase 6b-2, 0.261.249). `workflowAlertOpenRunPath` calls
   `v2WorkflowRunPath(scope, workflowId, runId)` from `lib/notificationLinks.ts`. There's
   no separate run page: it returns the run's address in its workflow's run history, the
   same address Open workflow named before. It returns `null` when the alert names no run

docs/explanation/release_notes.md

@@ -2,7 +2,7 @@
 
 For feature-focused and fix-focused drill-downs by version, see [Features by Version](https://github.com/microsoft/simplechat/tree/main/docs/explanation/features) and [Fixes by Version](https://github.com/microsoft/simplechat/tree/main/docs/explanation/fixes).
 
-### **(v0.261.239)**
+### **(v0.261.249)**
 
 #### New Features
 

docs/reference/chat-controls.md

@@ -587,7 +587,7 @@ for up to two minutes, and waits while the browser tab is hidden. When
 Microsoft 365 isn't connected for workflows, the card links to the connection in
 your profile, and while a run waits for Run as approval, it links to Approvals.
 
-Since **0.261.239**, a created card reads the workflow and its recent runs once
+Since **0.261.249**, a created card reads the workflow and its recent runs once
 to show **Next run** and **Last run**. It doesn't keep checking, so open the
 chat again to see a newer run. If that read fails, the card says "Run details
 aren't available right now."
@@ -628,15 +628,15 @@ A run takes one action at a time. While its **Cancel run** or **Retry** is waiti
 on the server, that run's **Cancel run**, **Retry** and **Review and approve** stay
 in place but do nothing, on the card and on the run's note in the chat.
 
-Runs are tracked since **0.261.239**. While a tracked run is in flight, V2
+Runs are tracked since **0.261.249**. While a tracked run is in flight, V2
 checks on it from any page, so the chat list and the bell stay current: first
 after 15 seconds, then less often, up to every 5 minutes. It pauses while the
 browser tab is hidden, unless desktop notifications are on, and stops checking
 once nothing is in flight.
 
 ### Results posted to the chat
 
-Implemented in **0.261.227**, with V2's controls in **0.261.239** (Refs:
+Implemented in **0.261.227**, with V2's controls in **0.261.249** (Refs:
 microsoft/simplechat#1546). When **Use Workflow Results In Chat**
 (`enable_chat_workflow_results`) is also on, a run started from chat posts its
 result, or a short note when it failed, was cancelled or can't be shown, back

functional_tests/test_support/workflowRunStatusFixtures.mjs

@@ -1,6 +1,6 @@
 // workflowRunStatusFixtures.mjs
-// Version: 0.261.239
-// Implemented in: 0.261.239
+// Version: 0.261.249
+// Implemented in: 0.261.249
 // Builds rows and responses in the exact shape of 6b-1's chat-started workflow run status route
 // (GET /api/v2/orchestration/workflow-runs/status, functions_workflow_chat_delivery_status.py),
 // for the V2 workflow run tests. Every key the route writes is present, so a test that drops or

functional_tests/test_v2_orchestration_workflow_run_links_xss_guardrail.py

@@ -2,9 +2,9 @@
 # test_v2_orchestration_workflow_run_links_xss_guardrail.py
 """
 Functional test for the V2 workflow run links passing the XSS sink guardrail.
-Version: 0.261.239
+Version: 0.261.249
 Implemented in: 0.261.212
-A group run's link built through the checked group path builder: 0.261.239
+A group run's link built through the checked group path builder: 0.261.249
 
 This test ensures that the Started workflows links under a chat answer pass
 scripts/check_xss_sinks.py the way CI runs it. The link component calls the