Area stewards: three invitations

[Fmarzochi]

EGC has had one maintainer since day one. As of today the docs say what that means and how it changes: docs/governance/stewards.md opens area stewardship. It is a role, not access: the first reviewer on pull requests that touch an area, the first triage on its issues, and the person who keeps its documentation honest. Merges, releases and repository settings stay with me, and any elevated access follows MAINTAINERS.md.

Three invitations, based on what each of you has already shipped:

• @Akisolu, Windows and OpenCode: dozens of Windows fixes and two rounds of real-machine bisects on OpenCode.
• @Tyr1onX, Session Mesh: the chaos and concurrency tests that hardened the bus.
• @kunaaaalcodes, Installer: the generic retirement (feat(install): retire the files a renamed or dropped command, prompt, rule or skill leaves behind, on every target #1426) and the shape transitions (fix(install): resolve source shape transitions at installed destinations (#1428) #1439).

If you accept, reply here and I will list you in the table with the date. If you would rather not, that is fine too; nothing changes about how welcome your pull requests are. Questions about the role go in this thread.

The same round published support levels, which says which tools I stand behind daily and which are community-supported, with the criteria, and the vision, which says where EGC is going and that the engine stays free.

[Akisolu]

Hi Felipe.

Thank you for this invitation — I've thought about it a lot before replying.

I'll be honest: I spent some time questioning whether I really deserved this. What settled it for me was yesterday's issue and PR (#1445 / #1447). Working through that timeout diagnosis with you, getting your feedback on my draft, and seeing the fix land on main reminded me that I've already been doing this work — and that I've been learning from every round of it. That's what convinced me to accept.

So yes: I accept the Windows and OpenCode stewardship. I'm grateful for the trust, and for the way you've guided me through every issue and PR so far — it's a big part of why I feel ready for this.

One thing I want to be upfront about: the university semester is starting, so my availability may dip at times, especially around exams. I'll do my best to stay on top of reviews and triage, and I'll let you know if I ever need to slow down.

Thanks again for inviting me into this role. Looking forward to it.

— Akisolu

[Fmarzochi]

Welcome aboard, Akisolu, and thank you for saying it the way you did. The doubt you describe is the mark of someone who takes the role seriously, and the record settles it: the Windows fixes, the OpenCode bisects, and this week's #1445 into #1447 are exactly the work a steward does.

Your acceptance is recorded today: the table in docs/governance/stewards.md moves you to accepted with 2026-09-14 in the next docs pull request.

On the semester: no fixed hours are attached to this. The role is first review on pull requests that touch Windows or OpenCode, first triage on their issues, and keeping their docs honest, at the pace your studies allow. When exams come, say so in a line and things keep moving; nothing waits on you alone, and nothing about being welcome here changes.

Glad to have you in this seat.

[Fmarzochi]

@Akisolu welcome aboard, and thank you. You earned it. The timeout round on #1445 and #1447 is exactly the kind of ownership this role is about: working the diagnosis through, taking the feedback, and keeping the fix honest on main. You are listed in docs/governance/stewards.md as the Windows and OpenCode steward, since 2026-09-14. The area is yours to keep honest: first review on the pull requests that touch it, first triage on its issues, and the docs that describe it. Merges, releases and repository settings stay with me.

The Session Mesh and Installer seats stay open for whenever the people who have shipped there want them. No pressure and no deadline, and nothing changes about how welcome anyone's pull requests are either way.

[Fmarzochi]

The Session Mesh and Installer invitations of 12 September had no answer in six weeks, so I am letting them lapse: both areas stay with me, and the table in docs/governance/stewards.md lists the Windows and OpenCode seat alone. Nothing changes about how welcome anyone's pull requests are, and sustained, merged work in an area is still the road to an invitation.

The role itself is wired now: .github/stewards.json carries each area's paths, a workflow requests the steward's review on every pull request that touches the area, and docs/governance/stewards.md says how triage and labels work. Closing this announcement; that page is the place to look from here on.