📝 council(ROOT): Restructure FCA responsibilities

The "Roles and Responsibilities" section undersold two structural
realities of the FCA seat and named one duty that the role had outgrown.
This commit restructures the section to fix both.

Add "Fedora Council and Governance" as its own subsection. Holding the
FCA seat itself was never listed as a responsibility in its own right,
even though every other duty in this charter flows from it. The Code of
Conduct Committee chair duties move here too, since they are a
governance-body membership function like the Council seat itself, and
their description is narrowed to match what the role actually does:
convening and coordinating meetings, following up on submitted cases in
a timely way, and serving as the Committee's secretary & documentarian.
The FCA does not uniquely drive Committee discussion or deliberation —
that responsibility is shared by all Committee members — so the previous
"uphold and champion psychological safety" and "primary liaison"
language overstated the role and has been replaced. The remaining
Council-documentation maintenance duty is also noted as done in close
consultation with the Fedora Operations Architect, currently @amoloney,
reflecting real overlap between the two roles on Council administration.

The Fedora Mindshare Committee chair duty stays in Budget Management,
where it already lived. The Mindshare Committee is a governance body,
but for the FCA's purposes it is functionally a fiduciary responsibility
— it is the body that reviews and approves community funding requests —
so it belongs with the rest of the budget-stewardship bullets rather
than under general governance.

Remove "Community Initiative Support" as a dedicated subsection. The
Fedora Council paused the Community Initiatives program pending a
redesigned process built with more community input (see ref below),
so a charter section built entirely around sponsoring and onboarding
those initiatives no longer describes real, ongoing work. Its one duty
that was not Initiative-specific — maintaining Council governance
documentation — survives, folded into the new Governance section above.

Remove "Collaboration with Community Ops" as a dedicated subsection. Its
content duplicated the CommOps entry already in the Communication
section's stakeholder list further down the page; keeping both meant the
same commitment was stated twice, once as a whole subsection and once as
a single bullet.

Add "CentOS Ecosystem Stewardship" as a new subsection. Fedora & CentOS
Stream are closely linked as sibling RPM-ecosystem projects, and the
FCA's existing governance and resource-stewardship work already touches
that relationship without ever naming it. So, this section makes it
explicit: representing Fedora's interests on the CentOS Board, serving
as a bridge between the two communities, organizing the CentOS Connect
contributor conference, and supporting communication between CentOS
Special Interest Groups and their partner ecosystem.

Ref: https://discussion.fedoraproject.org/t/fedora-council-statement-on-the-future-of-community-initiatives-and-the-ai-developer-desktop-proposal/195402

Assisted-by: Claude Sonnet 5 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>

council/modules/ROOT/pages/fca.adoc

@@ -18,6 +18,15 @@ The breadth of this role is intentional: the FCA operates across community gover
 
 The Fedora Community Architect has the following key responsibilities:
 
+[[roles-governance]]
+=== Fedora Council and Governance
+
+* Hold the FCA seat on the {team_name}, participating in decisions on project structure, trademarks, strategy, and conflict resolution.
+* Chair the xref:project:code-of-conduct:committee.adoc[Code of Conduct Committee], coordinating and convening its regular meetings and ensuring timely follow-up on cases submitted to the Committee.
+* Serve as the Code of Conduct Committee's secretary and documentarian, maintaining its charter, membership records, and case documentation.
+* Coordinate the publication of official Committee responses and annual transparency reports.
+* Maintain documentation related to {team_name} governance, policies, and procedures, coordinating the creation, revision, and publication of Council documents with Council members and the community, in close consultation with the xref:foa.adoc[Fedora Operations Architect].
+
 [[roles-budget]]
 === Budget Management
 
@@ -38,32 +47,14 @@ The Fedora Community Architect has the following key responsibilities:
 * Serve as the overall project manager for the conference, ensuring all functions remain synchronized and on schedule.
 * Curate a conference program that addresses key project challenges, showcases innovation, and creates a welcoming environment for all contributors.
 
-[[roles-initiatives]]
-=== Community Initiative Support
+[[roles-centos]]
+=== CentOS Ecosystem Stewardship
 
-* Serve as an executive sponsor for selected Community Initiatives, providing guidance and support to community leaders to ensure successful adoption and implementation.
-* Facilitate onboarding of Community Initiatives to the Fedora Council.
-* Maintain documentation related to Fedora Council governance, policies, and procedures.
-* Coordinate the creation and revision of Council documents, working with Council members to ensure accuracy and clarity.
-* Coordinate the publication and communication of Council documentation to the Fedora community.
-
-[[roles-commops]]
-=== Collaboration with Community Ops
-
-* Serve as the primary leader and advocate for the xref:commops::index.adoc[Fedora Community Ops Team].
-* Set the strategic direction for Community Ops to ensure its work in community enablement and analytics aligns with broader project goals.
-* Act as a primary advisor for Fedora teams seeking support from CommOps, connecting them with the appropriate resources.
-* Provide ethical and community-centric guidance for all Community Ops data analysis initiatives.
-* Facilitate trusted Community Ops members' access to the data, tooling, and resources required to support the health of the community.
-
-[[roles-coc]]
-=== Fedora Code of Conduct Committee Chair
-
-* Uphold and champion the psychological safety of the Fedora community.
-* Facilitate the xref:project:code-of-conduct:committee.adoc[Code of Conduct Committee]'s operations and regular meetings.
-* Present new cases to the Committee and act as the primary liaison between the Committee and the reporting party.
-* Coordinate the publication of official Committee responses and annual transparency reports.
-* Maintain the Committee's charter, membership records, and official documentation.
+* Represent Fedora's interests within the CentOS project, engaging with the CentOS Board on governance, elections, and community transitions.
+* Serve as a bridge between the Fedora and CentOS communities, sharing lessons, tooling, and processes across the upstream/downstream relationship.
+* Organize CentOS Connect, the project's annual contributor conference, coordinating logistics and programming with the CentOS community.
+* Advocate for CentOS Stream partners and users, surfacing their needs and feedback to the Fedora community and to Red Hat engineering.
+* Support open, transparent communication between CentOS Special Interest Groups (SIGs) and the broader partner ecosystem.
 
 
 [[current]]