Skip to content

docs(#128): update control labels table and example to list all 9 labels - #135

Merged
ralphbean merged 1 commit into
mainfrom
agent/128-update-control-labels-docs
Jul 13, 2026
Merged

docs(#128): update control labels table and example to list all 9 labels#135
ralphbean merged 1 commit into
mainfrom
agent/128-update-control-labels-docs

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Add missing rows for feature, question, bug, and documentation to the control labels table in docs/triage.md. Update the ready-to-code row to note that bug and documentation categories also receive their eponymous labels automatically. Update the example issue-labels skill snippet to list all 9 control labels instead of 5.

The CONTROL_LABELS array in scripts/post-triage.sh has 9 entries but the docs only listed 5. PRs #96 and #109 added bug and documentation to the array without updating the docs.


Closes #128

Post-script verification

  • Branch is not main/master (agent/128-update-control-labels-docs)
  • Secret scan passed (gitleaks — ef7e8c3c64b1a8af87aec2d253d26ea81a6310de..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Add missing rows for feature, question, bug, and documentation to
the control labels table in docs/triage.md. Update the ready-to-code
row to note that bug and documentation categories also receive their
eponymous labels automatically. Update the example issue-labels skill
snippet to list all 9 control labels instead of 5.

The CONTROL_LABELS array in scripts/post-triage.sh has 9 entries but
the docs only listed 5. PRs #96 and #109 added bug and documentation
to the array without updating the docs.

Closes #128
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 13, 2026 07:24
@ralphbean

Copy link
Copy Markdown
Member

/fs-review

@ralphbean
ralphbean added this pull request to the merge queue Jul 13, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Jul 13, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 11:49 AM UTC · Completed 11:57 AM UTC
Commit: bd28f41 · View workflow run →

Merged via the queue into main with commit 66cacea Jul 13, 2026
11 checks passed
@ralphbean
ralphbean deleted the agent/128-update-control-labels-docs branch July 13, 2026 11:51
@fullsend-ai-retro

fullsend-ai-retro Bot commented Jul 13, 2026

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 11:53 AM UTC · Completed 12:05 PM UTC
Commit: 421d852 · View workflow run →

@fullsend-ai-review

Copy link
Copy Markdown

Review skipped — this PR is already merged.

The /fs-review command only reviews open pull requests.

Posted by fullsend post-review check

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #135 — docs(#128): update control labels table

Timeline

Time (UTC) Event
07:09 Retro bot files issue #128 (doc drift found during retro on PR #109)
07:10–07:14 Triage agent runs (run 29231161890) — categorizes as documentation, labels ready-to-code
07:14–07:24 Code agent runs (run 29231423983) — implements fix, creates PR #135
07:24 Post-code script fails to apply ready-for-review label — ##[warning]Failed to apply ready-for-review label to PR #135
07:24–11:48 4.5-hour idle gap — no review agent dispatched, PR awaits human
11:48 Human posts /fs-review
11:49 Human approves PR (before review agent starts)
11:49 Review agent dispatched (run 29247566417)
11:51 PR merged
11:53 Review agent still in_progress (wasted compute)

What went well

The retro-to-code pipeline worked excellently. The retro agent on PR #109 identified documentation drift in the CONTROL_LABELS table, filed a well-scoped issue with specific locations and validation criteria, and the triage→code pipeline produced a correct 6-line fix in 14.5 minutes with zero rework. The code agent correctly identified all three places to update: the control labels table, the ready-to-code description, and the example snippet.

Evidence for existing issues

Assessment

No novel proposals — all identified improvements are tracked by existing open issues. The pipeline performed well for this class of change (docs-only, single-file, retro-filed). The primary bottleneck was the 4.5-hour wait for human review caused by the broken review auto-dispatch (fullsend-ai/fullsend#3996 + #3660).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update docs/triage.md control labels table and issue-labels example to match CONTROL_LABELS array

1 participant