swarm-controller: stop narrating pr review history in doc comments

This commit is contained in:
damocles 2026-08-31 18:33:25 +02:00 committed by mara
commit 586f7f68c2
2 changed files with 22 additions and 27 deletions

View file

@ -3,10 +3,9 @@
//! filtered). See [`crate::forge::Client::issue_report`] and
//! [`crate::forge::Client::issue_report_all`] for how a row's `blocked` /
//! `depended_on_by_count` fields are actually computed; this module is
//! just the HTTP surface over that logic, split out into its own file per
//! mara's review call on the PR that introduced it (same shape
//! [`crate::webhook`] already uses: business logic in
//! `crate::forge::Client`, the axum handlers next to their own routes).
//! just the HTTP surface over that logic, split out into its own file —
//! same shape [`crate::webhook`] already uses: business logic in
//! `crate::forge::Client`, the axum handlers next to their own routes.
use axum::{
Json,
@ -17,12 +16,11 @@ use super::{AppState, StatusUnavailable};
use crate::forge;
/// Repos with at least one open issue, as `owner/name` full names — the
/// data source for swarm-ui's repo-filter dropdown (mara: "repo filter
/// should be dropdown (list only repos with open issues)"). Not scoped to
/// [`forge::CONFIG_ORG`] the way `main.rs`'s `get_config_prs` is: mara's
/// own framing for this issue-report page was "repos cannot be fixed for
/// a hyperhive feature", so this deliberately covers the whole forge
/// instance, not one org.
/// data source for swarm-ui's repo-filter dropdown. Not scoped to
/// [`forge::CONFIG_ORG`] the way `main.rs`'s `get_config_prs` is: this
/// report deliberately covers the whole forge instance, not one org, since
/// the report itself is a general-purpose browsing tool rather than
/// something agent-config-specific.
#[utoipa::path(
get,
path = "/api/repos",
@ -51,9 +49,8 @@ pub async fn get_repos(
}
/// Every open issue across every repo with at least one — the default,
/// no-repo-filter view (mara: "by default, i want it to not filter by
/// repo"). See [`get_issue_report`] for the single-repo counterpart (used
/// once the dropdown's repo filter is set) and
/// no-repo-filter view. See [`get_issue_report`] for the single-repo
/// counterpart (used once the dropdown's repo filter is set) and
/// [`forge::Client::issue_report_all`] for how the fan-out works.
#[utoipa::path(
get,