[docs] os version support

[Jeff Whiteside (jsidewhite)]

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Incorrect release labels and update links could direct consumers to updates for the wrong Windows release.

Review effort: Balanced
Findings: None

What changed in this PR

Replaces the detailed ProcessContainer enforcement reference with a Windows support matrix covering both process and session isolation.

Changes:

• Adds release-specific build numbers and Windows update links for both backends.
• Removes the previous enforcement-tier and policy-capability documentation.

File	Description
docs/​backends/​process-container/​os-version-support.md	Replaces capability details with a two-backend Windows support table.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Incorrect release labels and mismatched update links would direct readers to the wrong Windows updates.

Review effort: Balanced
Findings: None

Previously missed (1)

In code that hasn't changed since last review

Correct reversed Windows release labels and 26300.9550 links

docs/​backends/​process-container/​os-version-support.md:14

The release labels are reversed: Microsoft's release information maps the 28000 builds to 26H1 and 26300.9550 to 26H2. Both links in the 26300.9550 row also point to 28000-series 26H1 updates, so they do not provide the advertised build. Label the 28000 row 26H1 and the 26300 row 26H2, and replace the latter's links with verified references for 26300.9550 so readers can select the correct updates.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Release/build mappings and update links need correction, and existing documentation still points to the removed policy-support reference.

Review effort: Balanced
Findings: None

Previously missed (2)

In code that hasn't changed since last review

Preserve or update policy-support documentation references

docs/​backends/​process-container/​os-version-support.md:3

Replacing the policy-support reference with a build table leaves existing documentation pointing to information that is no longer here. README.md:41 and docs/development/guides/process-container-adding-os-features.md:13–14 still direct readers here for per-release filesystem, network, and UI policy support. The new table does not explain those capabilities or their enforcement-tier requirements. Retain that reference alongside the table, or relocate it and update the referring documentation in the same change.

Correct reversed Windows release labels and mismatched update links

docs/​backends/​process-container/​os-version-support.md:12

The 26H1 and 26H2 release labels are reversed, and the update links do not match the displayed builds. Microsoft's KB5120996 and KB5124006 correspond to 26H1 builds 28000.2804 and 28000.3086; KB5124010 includes 26H2 build 26300.9550. Correct both labels and their links so readers are directed to the update for their Windows release.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Support prerequisites remain ambiguous, and existing documentation links still promise the removed capability guidance.

Review effort: Balanced
Findings: None

Previously missed (2)

In code that hasn't changed since last review

Restore policy limitation guidance and update broken documentation links

docs/​backends/​process-container/​os-version-support.md:3

This replacement removes the per-release filesystem, network, and UI enforcement reference still promised by README.md:41, docs/development/guides/process-container-adding-os-features.md:13–14, and tests/playground/playground-limitations.md:5–7. Those links now lead only to build numbers, which do not explain policy limitations. Retain or relocate the relevant capability guidance and update these incoming links to its location.

Clarify build prerequisites and reconcile README minimum versions

docs/​backends/​process-container/​os-version-support.md:9

Please define whether these revisions are minimum supported builds, native-feature availability builds, or tested builds. README.md:28 still lists minimum builds of 26100 for processcontainer and 26340.9212 (Insider Preview) for isolation_session. If this table defines new backend minimums, reconcile the README; if it describes native-feature availability, distinguish that from backend support through AppContainer fallback. As written, consumers cannot determine which prerequisites to follow.