[Fmarzochi]

Why

The Session Mesh and Installer steward invitations of 2026-09-12 (Discussion #1442) had no answer in six weeks. Rather than renew them, this lets them lapse: both areas stay with the maintainer, and the discussion is closed with the note that says so.

What changes

• docs/governance/stewards.md: the table keeps the Windows and OpenCode seat alone; the sentence under it records the lapse and the date.
• .github/stewards.json: the two invited areas are gone, so the file and the table agree again (tests/ci/request-steward-review.test.js enforces that).
• CHANGELOG.md and docs/ROADMAP.md: one sentence each on the lapse, next to the feat(governance): ask the area steward for a review on pull requests that touch the area #2019 entry.

Nothing about the review automation changes: invited areas were never asked for a review, so the workflow's behavior is identical before and after.

Proof

• node tests/ci/request-steward-review.test.js: 11 passed, 0 failed, including the JSON versus table check and the tracked-files check for the remaining area.
• Local gate on the tree: no changed JS/TS files, exit 0.
• No em or en dash in the edited files.

---

Summary by cubic

Lets the Session Mesh and Installer steward invitations of 2026-09-12 (Discussion #1442) lapse after six weeks without an answer. Both areas stay with the maintainer, and the discussion is closed with a note recording that.

• Removes the two invited areas from .github/stewards.json so the file agrees with the stewards table, as the CI test enforces.
• Notes the lapse and date in docs/governance/stewards.md, CHANGELOG.md, and docs/ROADMAP.md.
• Review automation is unchanged: invited areas were never asked for reviews, so the workflow behaves identically.

^{Written for commit 39a4aa9. Summary will update on new commits.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud