Triage bot daily report — 2026-09-07 #2829

🤖 Automated message from Kaan's Automated Triage Bot.

stellar-docs bot activity — 2026-09-07

This was the first full day of the docs lanes running live. The bot reviews, comments, labels and opens PRs. It does not approve, merge or close. Those steps stay with a maintainer.

Waiting for a maintainer

Two items are blocked and need a decision:

• #2808 adds allow-unsafe-pr-checkout: true to the PR preview checkout. This lets a fork head build in a base repo context. The org membership gate runs first, but the risk is a policy choice. Label: bot:blocked-security.
• #2370 documents SDP endpoints GET /reports/statement and GET /reports/payment/{id}. These routes do not exist in the public SDP repos. Label: bot:needs-decision.

Eight PRs are verified and ready to merge: #2760, #2789, #2796, #2806, #2815, #2823, #2824, #2825.

Two PRs are close candidates: #2809 (preview test PR, the diff is one stray space in the root README) and #2241 (branch sync PR, merging it now reverts 2,366 files).

PR reviews

The bot reviewed 12 PRs and pushed fixes to three of them.

• #2815, the cargo-afl fuzzing guide, did not work as written. The bot adjudicated 16 Copilot points over 5 rounds, accepted 12 and rejected 4, and pushed 4 commits. The main defects were a missing crate-type step, an unbounded fuzz input that made AFL++ abort during seed calibration, and a monotonicity assert that never ran because last was never updated.
• #2823 got 2 fix commits after a check against stellar-core v28.0.1.
• #2824 got 1 precision commit. The bot also changed the PR body from "Closes 📝 Punctualize, stylize CLI Guide #1013" to "Refs 📝 Punctualize, stylize CLI Guide #1013", because two parts of that issue stay open.

New PRs from issues

The bot opened 4 PRs:

• #2823 documents CRITICAL validator quality (issue Incomplete description of automatic Quorum Set generation #985).
• #2824 documents which docs/tools/cli/ pages the build generates (issue 📝 Punctualize, stylize CLI Guide #1013).
• #2825 documents which contract errors try_call can recover from (issue Document recoverable versus nonrecoverable contract errors #1074).
• #2826 warns about unbounded collections in one contract data entry (issue Discuss harmful / easy mistakes that don't scale or could result in stuck contracts #1445).

Issue triage

The bot triaged 22 open issues, oldest first.

• 13 issues need a maintainer decision: Add env host function interface to docs generated from env.json #489, Streamline events related content #484, json-rpc code snippets should use stellar sdks #441, Provide code examples to make http requests using Stellar SDK in docs #404, Provide examples for each payment type on the /payments endpoint #680, Add page(s) about how to to script deployments, invokes, etc and other ops tasks #814, Document using a different source account for an operation that is different from the parent transaction envelope account #1022, Reference ingest library case-studies aka CDP hackathon projects #1330, Document horizon deprecation vision/plan #1331, Reorganize RPC+SDK related content in Guides section #1335, Add live request/response capabilities to the RPC methods docs #1365, Documentation on onboarding Solana Developers #1470, Update all Stellar How-To guides to use RPC instead of Horizon #1529. Most are old planning tickets. Later work answered some sub-items and contradicted others, so each needs a scope call.
• 2 issues need content from their author: Add Horizon triage FAQ to Horizon section of the docs #505 (the linked Google Doc returns 401) and Embed a video tutorial for Hubble #1338 (no video IDs).
• 3 issues already have a human owner, so the bot stood down: Refresh all "classic" How-To Guides & refresh the Channel Accounts section #338, 📒 Draw account summary codeblocks #870, 📹 Incorporate old meeting recordings #1087.