From 2504d6f8f8f19e64a116962a1eaa1784c7bb3948 Mon Sep 17 00:00:00 2001 From: fullsend-code <278716306+fullsend-ai-coder[bot]@users.noreply.github.com> Date: Tue, 11 Aug 2026 18:51:06 +0000 Subject: [PATCH 1/2] docs(#6113): surface org-mode deprecation in agent-visible files AGENTS.md had no mention of the per-org installation mode deprecation (ADR 0044), so agents generated and reviewed org-mode content as if it were active architecture. Add a bullet to the "How to work in this repo" section instructing agents not to add org-mode-specific content and to flag existing org-mode references as deprecated. Also annotate the org-mode reference in docs/agents/triage.md (line 73) with an inline deprecation note and link to ADR 0044, so the triage agent documentation reflects the current state. Note: pre-commit could not run in-sandbox (network policy blocks git fetch for hook environment setup). The post-script runs pre-commit authoritatively on the runner. Closes #6113 --- AGENTS.md | 1 + docs/agents/triage.md | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 403db843e1..6b01ea5667 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -19,6 +19,7 @@ Fullsend is a platform for fully autonomous agentic development for Git-hosted o - When adding a new doc under `docs/`, check `docs/.vitepress/config.ts` sidebar config. Sections using `getMarkdownFiles()` are auto-discovered. All other sections need a manual `{ text, link }` entry. Also add the new folder's prefix to `search.options.scopes` in the same file so the folder's pages are reachable when search scope pills are active. - When removing, renaming, or changing the behavior or output format of a CLI command, public API, or user-facing feature, grep all documentation files under `docs/` for references and update them to reflect the current behavior. Pay special attention to `docs/cli/`, `docs/guides/`, and any getting-started or operations guides. - When adding a new skill under `skills/`, check the user-facing guides for relevant cross-reference opportunities: `docs/guides/user/customizing-with-skills.md` (skill catalog and usage), `docs/guides/user/bring-your-own-agent.md` (agent composition and tuning), and `docs/guides/README.md` (guide index). Add a brief cross-reference or section pointer if the new skill fills a gap in those guides. +- Per-org installation mode is deprecated ([ADR 0044](docs/ADRs/0044-deprecate-per-org-installation-mode.md)) and will be removed in v2.0. Do not add org-mode-specific content to docs or code. When reviewing PRs that reference org mode, flag it as deprecated rather than engaging with org-mode details as active architecture. Per-repo is the sole supported installation model going forward. ## Topic-specific guidance diff --git a/docs/agents/triage.md b/docs/agents/triage.md index d2eedcb448..b7b1921138 100644 --- a/docs/agents/triage.md +++ b/docs/agents/triage.md @@ -70,7 +70,8 @@ create_issues: - upstream-org/specific-repo ``` -**Defaults:** At install time, fullsend populates this with your org (in org mode) +**Defaults:** At install time, fullsend populates this with your org (in org mode, +[deprecated](../ADRs/0044-deprecate-per-org-installation-mode.md)) or your repo (in per-repo mode), plus `fullsend-ai/fullsend` as an upstream target. **When to expand the allowlist:** If your project depends on libraries or services From 932a6760a2ea35c2e8de55f476ce61b9720cfbf4 Mon Sep 17 00:00:00 2001 From: Wayne Sun Date: Wed, 19 Aug 2026 14:29:58 -0400 Subject: [PATCH 2/2] docs(#6113): make deprecation status explicit for humans and agents MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The original bullet said per-org mode is deprecated but didn't call out that the rule applies to human contributors as well as agents. waynesun09 noted on #6113 that the generic phrasing already failed to prevent recurrence on PR #6375, so make the instruction explicit: don't add or extend org-mode-specific content, and flag it as deprecated rather than active architecture when reviewing. Deliberately don't link a specific tracking issue for the command removal inventory: #2302 (originally linked) closed and split into #6390-#6392, and #6391 (the deprecation-warning issue that enumerated the commands) closed as not-planned when the team decided to remove per-org support directly instead of warning first. Issue state churns too fast for a rule file to track — the ADR link is stable and durable in a way a specific issue number is not, so point only to ADR 0044 and let it be the single source of truth for removal scope. Apply the same clarification to the docs/agents/triage.md annotation so it reads consistently with AGENTS.md. Signed-off-by: Wayne Sun Assisted-by: Claude --- AGENTS.md | 2 +- docs/agents/triage.md | 4 +--- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 6b01ea5667..1337f4a5be 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -19,7 +19,7 @@ Fullsend is a platform for fully autonomous agentic development for Git-hosted o - When adding a new doc under `docs/`, check `docs/.vitepress/config.ts` sidebar config. Sections using `getMarkdownFiles()` are auto-discovered. All other sections need a manual `{ text, link }` entry. Also add the new folder's prefix to `search.options.scopes` in the same file so the folder's pages are reachable when search scope pills are active. - When removing, renaming, or changing the behavior or output format of a CLI command, public API, or user-facing feature, grep all documentation files under `docs/` for references and update them to reflect the current behavior. Pay special attention to `docs/cli/`, `docs/guides/`, and any getting-started or operations guides. - When adding a new skill under `skills/`, check the user-facing guides for relevant cross-reference opportunities: `docs/guides/user/customizing-with-skills.md` (skill catalog and usage), `docs/guides/user/bring-your-own-agent.md` (agent composition and tuning), and `docs/guides/README.md` (guide index). Add a brief cross-reference or section pointer if the new skill fills a gap in those guides. -- Per-org installation mode is deprecated ([ADR 0044](docs/ADRs/0044-deprecate-per-org-installation-mode.md)) and will be removed in v2.0. Do not add org-mode-specific content to docs or code. When reviewing PRs that reference org mode, flag it as deprecated rather than engaging with org-mode details as active architecture. Per-repo is the sole supported installation model going forward. +- **Per-org installation mode is deprecated** ([ADR 0044](docs/ADRs/0044-deprecate-per-org-installation-mode.md)) and is being removed. This applies to human contributors and agents alike: do not add or extend org-mode-specific content in docs or code, and when reviewing a PR that touches org-mode content, flag it as referencing deprecated functionality rather than engaging with the org/repo-mode distinction as active architecture. Per-repo is the sole supported installation model going forward. ## Topic-specific guidance diff --git a/docs/agents/triage.md b/docs/agents/triage.md index b7b1921138..cbb7c2b02f 100644 --- a/docs/agents/triage.md +++ b/docs/agents/triage.md @@ -70,9 +70,7 @@ create_issues: - upstream-org/specific-repo ``` -**Defaults:** At install time, fullsend populates this with your org (in org mode, -[deprecated](../ADRs/0044-deprecate-per-org-installation-mode.md)) -or your repo (in per-repo mode), plus `fullsend-ai/fullsend` as an upstream target. +**Defaults:** At install time, fullsend populates this with your org (in org mode — **deprecated**, see [ADR 0044](../ADRs/0044-deprecate-per-org-installation-mode.md)) or your repo (in per-repo mode), plus `fullsend-ai/fullsend` as an upstream target. **When to expand the allowlist:** If your project depends on libraries or services in other GitHub orgs and you want the triage agent to automatically file