docs(ladder): request roles via issues in fullsend-ai/org

Triage, Write, and Maintainer role requests are now issues in
fullsend-ai/org (triage-request/write-request/maintainer-request
templates), approved by adding the requester to the triagers/writers/core
teams in peribolos.yaml. Write requests need two maintainers approving by
commenting on the request issue before the peribolos.yaml PR is opened,
and that PR links the approved issue. Maintainer nominations follow the
MAINTAINERS.md process: maintainer consensus, then the core team.

That repo's notify-role-request-slack workflow handles Slack
notifications, so trim notify-vouch-slack to vouch requests only.

Assisted-By: glm-5-3(pi)
Signed-off-by: Hector Martinez <hemartin@redhat.com>

Author: rh-hemartin

.github/DISCUSSION_TEMPLATE/triage-request.yml

@@ -24,9 +24,7 @@ jobs:
     if: >-
       github.repository_owner == 'fullsend-ai' &&
       (github.event_name == 'workflow_dispatch' ||
-      github.event.discussion.category.slug == 'vouch-request' ||
-      github.event.discussion.category.slug == 'triage-request' ||
-      github.event.discussion.category.slug == 'write-request')
+      github.event.discussion.category.slug == 'vouch-request')
     runs-on: ubuntu-24.04
     timeout-minutes: 5
     steps:
@@ -58,16 +56,6 @@ jobs:
               request_emoji="🤝"
               request_context="Review the request and comment \`/vouch\` to approve."
               ;;
-            triage-request)
-              request_label="triage request"
-              request_emoji="🔎"
-              request_context="Review the request for triage access."
-              ;;
-            write-request)
-              request_label="write request"
-              request_emoji="✍️"
-              request_context="Review the request for write access."
-              ;;
             *)
               echo "::error::Invalid discussion category received"
               exit 1

.github/DISCUSSION_TEMPLATE/write-request.yml

@@ -73,14 +73,15 @@ repository.
 - Responsive to feedback on your contributions — on changes you drove
   and in review discussions you took part in
 
-**How to check:** You are a member of
-[@fullsend-ai/triagers](https://github.com/orgs/fullsend-ai/teams/triagers).
+**How to check:** Your GitHub username is listed under `triagers`
+in the `teams:` section of
+[peribolos.yaml](https://github.com/fullsend-ai/org/blob/main/peribolos.yaml)
+in the [fullsend-ai/org](https://github.com/fullsend-ai/org) repository.
 
 **How to request:** Open a
-[Triage Request](https://github.com/fullsend-ai/fullsend/discussions/new?category=triage-request)
-discussion. Link to your substantive reviews or merged PRs, and briefly
-describe the work and judgment each one shows (see
-[Making your case](#making-your-case)).
+[Triage Request](https://github.com/fullsend-ai/org/issues/new?template=triage-request.yml)
+issue in [fullsend-ai/org](https://github.com/fullsend-ai/org). A maintainer
+approves by adding your username to the `triagers` team in `peribolos.yaml`.
 
 You do not need to be an expert in the codebase or community conventions
 to request Triage. If you think your contributions demonstrate
@@ -113,15 +114,21 @@ repository.
   PR workflow, review etiquette)
 - Trusted not to push directly to protected branches or bypass review
 
-**How to check:** You are a member of
-[@fullsend-ai/writers](https://github.com/orgs/fullsend-ai/teams/writers).
+**How to check:** Your GitHub username is listed under `writers`
+in the `teams:` section of
+[peribolos.yaml](https://github.com/fullsend-ai/org/blob/main/peribolos.yaml)
+in the [fullsend-ai/org](https://github.com/fullsend-ai/org) repository.
 
 **How to request:** Open a
-[Write Request](https://github.com/fullsend-ai/fullsend/discussions/new?category=write-request)
-discussion. Link to your contribution history and describe the work
-and judgment it demonstrates (see [Making your case](#making-your-case)).
-
-**Who approves:** Two maintainers must approve. A single maintainer
+[Write Request](https://github.com/fullsend-ai/org/issues/new?template=write-request.yml)
+issue in [fullsend-ai/org](https://github.com/fullsend-ai/org). Two maintainers
+must approve by commenting on that issue; only after both approvals should
+a `peribolos.yaml` PR be opened. The maintainer opening the PR links the
+approved issue in the PR description, and adds your username to the `writers`
+team in `peribolos.yaml`.
+
+**Who approves:** Two maintainers must approve on the request issue before
+the `peribolos.yaml` PR is opened. A single maintainer
 can request more discussion but cannot unilaterally grant write access.
 
 ### Maintainer
@@ -140,6 +147,17 @@ project and to help review contributions you are not driving.
 **Criteria and process:** See [MAINTAINERS.md](MAINTAINERS.md) for the
 full eligibility criteria, nomination process, and time commitment.
 
+**How to check:** Your GitHub username is listed under `maintainers`
+of the `core` team in
+[peribolos.yaml](https://github.com/fullsend-ai/org/blob/main/peribolos.yaml)
+in the [fullsend-ai/org](https://github.com/fullsend-ai/org) repository.
+
+**How to request:** Open a
+[Maintainer Nomination](https://github.com/fullsend-ai/org/issues/new?template=maintainer-request.yml)
+issue in [fullsend-ai/org](https://github.com/fullsend-ai/org). Existing
+maintainers discuss and reach consensus; if approved, your username is
+added to the `core` team in `peribolos.yaml`.
+
 ## Demonstrating readiness
 
 Advancement is a human assessment of demonstrated trust and readiness.
@@ -237,9 +255,9 @@ Role changes use the following request mechanisms:
 | Role | Request mechanism | Approval |
 |------|-------------------|----------|
 | Vouched | [Vouch Request](https://github.com/fullsend-ai/fullsend/discussions/new?category=vouch-request) | 1 Maintainer |
-| Triage | [Triage Request](https://github.com/fullsend-ai/fullsend/discussions/new?category=triage-request) | 1 Maintainer |
-| Write | [Write Request](https://github.com/fullsend-ai/fullsend/discussions/new?category=write-request) | 2 Maintainers |
-| Maintainer | Issue (see [MAINTAINERS.md](MAINTAINERS.md)) | Maintainer consensus |
+| Triage | [Triage Request](https://github.com/fullsend-ai/org/issues/new?template=triage-request.yml) issue in [fullsend-ai/org](https://github.com/fullsend-ai/org) | 1 Maintainer |
+| Write | [Write Request](https://github.com/fullsend-ai/org/issues/new?template=write-request.yml) issue in [fullsend-ai/org](https://github.com/fullsend-ai/org) | 2 Maintainers |
+| Maintainer | [Maintainer Nomination](https://github.com/fullsend-ai/org/issues/new?template=maintainer-request.yml) issue in [fullsend-ai/org](https://github.com/fullsend-ai/org) (see [MAINTAINERS.md](MAINTAINERS.md)) | Maintainer consensus |
 
 ## Revoking access
 

.github/workflows/notify-vouch-slack.yml

@@ -33,8 +33,10 @@ own establish the familiarity needed for a maintainer role.
 
 ## Process
 
-1. **File an issue** titled "Maintainer nomination: \<your GitHub
-   handle\>". In the issue, link to merged PRs you have authored or
+1. **File a nomination issue** using the
+   [Maintainer Nomination](https://github.com/fullsend-ai/org/issues/new?template=maintainer-request.yml)
+   template in [fullsend-ai/org](https://github.com/fullsend-ai/org).
+   In the issue, link to merged PRs you have authored or
    substantive reviews you have provided that demonstrate your
    familiarity with the project.
 2. **Current maintainers discuss.** The maintainers will review your