Skip to content

t1312: Remove dead code stubs + retire evaluate_worker heuristic tree#2221

Merged
marcusquinn merged 1 commit intomainfrom
refactor/t1312-dead-code-evaluate
Feb 24, 2026
Merged

t1312: Remove dead code stubs + retire evaluate_worker heuristic tree#2221
marcusquinn merged 1 commit intomainfrom
refactor/t1312-dead-code-evaluate

Conversation

@marcusquinn
Copy link
Copy Markdown
Owner

Summary

  • Delete lifecycle.sh (102 lines) and git-ops.sh (91 lines) — all functions were no-op stubs, never called
  • Remove evaluate_worker() (687 lines), evaluate_with_ai() (251 lines), and evaluate_worker_with_metadata() (58 lines) from evaluate.sh — deterministic heuristic tree replaced by AI-powered assess_task_with_metadata() in assess-task.sh
  • Update pulse.sh to call assess_task_with_metadata() directly (remove 3-tier fallback chain)
  • Update cmd_evaluate CLI, comment references in dispatch.sh and deploy.sh

Net: -977 lines (1,008 deleted, 31 added)

Part of t1311 (Supervisor AI-first migration). Closes #2208.

…stic tree

Delete lifecycle.sh (102 lines) and git-ops.sh (91 lines) — all functions
were no-op stubs, never called.

Remove evaluate_worker() (687 lines), evaluate_with_ai() (251 lines), and
evaluate_worker_with_metadata() (58 lines) from evaluate.sh. These formed
a deterministic heuristic tree for worker evaluation. Replaced by
assess_task_with_metadata() in assess-task.sh (AI-powered, already the
preferred path in pulse.sh since it was added).

Update pulse.sh to call assess_task_with_metadata() directly instead of
the 3-tier fallback chain. Update cmd_evaluate CLI to use the AI path.
Update comment references across dispatch.sh and deploy.sh.

Net: -977 lines (1,008 deleted, 31 added)
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 24, 2026

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 22 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 69011d7 and 48bf1e6.

📒 Files selected for processing (7)
  • .agents/scripts/supervisor/assess-task.sh
  • .agents/scripts/supervisor/deploy.sh
  • .agents/scripts/supervisor/dispatch.sh
  • .agents/scripts/supervisor/evaluate.sh
  • .agents/scripts/supervisor/git-ops.sh
  • .agents/scripts/supervisor/lifecycle.sh
  • .agents/scripts/supervisor/pulse.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch refactor/t1312-dead-code-evaluate

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 45 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 24 17:25:15 UTC 2026: Code review monitoring started
Tue Feb 24 17:25:16 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 45

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 45
  • VULNERABILITIES: 0

Generated on: Tue Feb 24 17:25:18 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on removing dead code and replacing a deterministic heuristic tree with an AI-powered task assessment system. This change simplifies the evaluation process and reduces the codebase size, while also improving the accuracy and efficiency of task assessments.

Highlights

  • Code Removal: Removed dead code stubs (lifecycle.sh, git-ops.sh) and the evaluate_worker heuristic tree from evaluate.sh, resulting in a significant reduction in lines of code.
  • AI-Powered Task Assessment: The deterministic heuristic tree for worker evaluation has been replaced by an AI-powered assess_task_with_metadata() function in assess-task.sh.
  • Direct AI Evaluation: The pulse.sh script has been updated to call assess_task_with_metadata() directly, removing the previous fallback chain.
  • CLI Update: The cmd_evaluate CLI command has been updated, and references in dispatch.sh and deploy.sh have been commented.
Activity
  • Removal of dead code stubs.
  • Replacement of the evaluate_worker heuristic tree with AI-powered assessment.
  • Update of pulse.sh to directly call assess_task_with_metadata().
  • Update of cmd_evaluate CLI and comment references in dispatch.sh and deploy.sh.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request successfully removes dead code stubs and transitions the task evaluation to an AI-powered approach. The changes are well-documented within the code comments, clearly indicating the removal of the old heuristic tree and the adoption of assess_task_with_metadata(). The updates in deploy.sh, dispatch.sh, and pulse.sh correctly reflect this change, ensuring consistency across the supervisor scripts. The overall impact is a significant reduction in code lines and a move towards a more modern, AI-driven evaluation system. The removal of lifecycle.sh and git-ops.sh stubs is also a good cleanup, as they were unused.

@marcusquinn marcusquinn merged commit e59bc4c into main Feb 24, 2026
11 checks passed
@marcusquinn marcusquinn deleted the refactor/t1312-dead-code-evaluate branch February 24, 2026 17:30
marcusquinn added a commit that referenced this pull request Feb 24, 2026
marcusquinn added a commit that referenced this pull request Mar 14, 2026
…hived pulse.sh

The heartbeat_window arithmetic at line 230 would emit a bash arithmetic error
if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer value (e.g. '90s'). Add a
regex guard that defaults to 90 and logs a warning when the value is non-numeric.

Note: the critical evaluate.sh heartbeat cleanup scope bug (the other finding
from issue #3364 / PR #1958 review) was already resolved — evaluate_with_ai()
containing the buggy push_cleanup/save_cleanup_scope ordering was deleted in
PR #2221 (t1312 dead code removal) before the supervisor was archived in
PR #2291. No change needed to evaluate.sh.

Shellcheck: evaluate.sh passes clean (0 violations). pulse.sh passes bash -n
syntax check; shellcheck OOMs on the 3983-line archived file (pre-existing,
unrelated to this change).

Closes #3364
alex-solovyev added a commit that referenced this pull request Mar 14, 2026
…e.sh

PR #1958 review feedback (CodeRabbit nitpick): arithmetic expansion on
heartbeat_window fails if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer
(e.g. '90s'). Add a regex guard that defaults to 90 and logs a warning
when the value is non-numeric.

Note: the critical finding (heartbeat cleanup scope ordering in evaluate.sh)
was already resolved by t1312 (PR #2221), which removed the heartbeat/watchdog
code entirely from the active supervisor path before archiving.

Closes #3364
alex-solovyev pushed a commit that referenced this pull request Mar 14, 2026
…hived pulse.sh (#4572)

The heartbeat_window arithmetic at line 230 would emit a bash arithmetic error
if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer value (e.g. '90s'). Add a
regex guard that defaults to 90 and logs a warning when the value is non-numeric.

Note: the critical evaluate.sh heartbeat cleanup scope bug (the other finding
from issue #3364 / PR #1958 review) was already resolved — evaluate_with_ai()
containing the buggy push_cleanup/save_cleanup_scope ordering was deleted in
PR #2221 (t1312 dead code removal) before the supervisor was archived in
PR #2291. No change needed to evaluate.sh.

Shellcheck: evaluate.sh passes clean (0 violations). pulse.sh passes bash -n
syntax check; shellcheck OOMs on the 3983-line archived file (pre-existing,
unrelated to this change).

Closes #3364
alex-solovyev added a commit that referenced this pull request Mar 14, 2026
…e.sh

PR #1958 review feedback (CodeRabbit nitpick): arithmetic expansion on
heartbeat_window fails if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer
(e.g. '90s'). Add a regex guard that defaults to 90 and logs a warning
when the value is non-numeric.

Note: the critical finding (heartbeat cleanup scope ordering in evaluate.sh)
was already resolved by t1312 (PR #2221), which removed the heartbeat/watchdog
code entirely from the active supervisor path before archiving.

Closes #3364
alex-solovyev added a commit that referenced this pull request Mar 14, 2026
…e.sh (#4581)

PR #1958 review feedback (CodeRabbit nitpick): arithmetic expansion on
heartbeat_window fails if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer
(e.g. '90s'). Add a regex guard that defaults to 90 and logs a warning
when the value is non-numeric.

Note: the critical finding (heartbeat cleanup scope ordering in evaluate.sh)
was already resolved by t1312 (PR #2221), which removed the heartbeat/watchdog
code entirely from the active supervisor path before archiving.

Closes #3364
marcusquinn added a commit that referenced this pull request Mar 14, 2026
…hived pulse.sh (#4572)

The heartbeat_window arithmetic at line 230 would emit a bash arithmetic error
if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer value (e.g. '90s'). Add a
regex guard that defaults to 90 and logs a warning when the value is non-numeric.

Note: the critical evaluate.sh heartbeat cleanup scope bug (the other finding
from issue #3364 / PR #1958 review) was already resolved — evaluate_with_ai()
containing the buggy push_cleanup/save_cleanup_scope ordering was deleted in
PR #2221 (t1312 dead code removal) before the supervisor was archived in
PR #2291. No change needed to evaluate.sh.

Shellcheck: evaluate.sh passes clean (0 violations). pulse.sh passes bash -n
syntax check; shellcheck OOMs on the 3983-line archived file (pre-existing,
unrelated to this change).

Closes #3364
marcusquinn pushed a commit that referenced this pull request Mar 14, 2026
…e.sh (#4581)

PR #1958 review feedback (CodeRabbit nitpick): arithmetic expansion on
heartbeat_window fails if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer
(e.g. '90s'). Add a regex guard that defaults to 90 and logs a warning
when the value is non-numeric.

Note: the critical finding (heartbeat cleanup scope ordering in evaluate.sh)
was already resolved by t1312 (PR #2221), which removed the heartbeat/watchdog
code entirely from the active supervisor path before archiving.

Closes #3364
alex-solovyev added a commit that referenced this pull request Mar 14, 2026
… quality-debt) (#4582)

* fix(t3364): add numeric validation for SUPERVISOR_EVAL_TIMEOUT in archived pulse.sh (#4572)

The heartbeat_window arithmetic at line 230 would emit a bash arithmetic error
if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer value (e.g. '90s'). Add a
regex guard that defaults to 90 and logs a warning when the value is non-numeric.

Note: the critical evaluate.sh heartbeat cleanup scope bug (the other finding
from issue #3364 / PR #1958 review) was already resolved — evaluate_with_ai()
containing the buggy push_cleanup/save_cleanup_scope ordering was deleted in
PR #2221 (t1312 dead code removal) before the supervisor was archived in
PR #2291. No change needed to evaluate.sh.

Shellcheck: evaluate.sh passes clean (0 violations). pulse.sh passes bash -n
syntax check; shellcheck OOMs on the 3983-line archived file (pre-existing,
unrelated to this change).

Closes #3364

* fix: guard SUPERVISOR_EVAL_TIMEOUT against non-numeric values in pulse.sh (#4581)

PR #1958 review feedback (CodeRabbit nitpick): arithmetic expansion on
heartbeat_window fails if SUPERVISOR_EVAL_TIMEOUT is set to a non-integer
(e.g. '90s'). Add a regex guard that defaults to 90 and logs a warning
when the value is non-numeric.

Note: the critical finding (heartbeat cleanup scope ordering in evaluate.sh)
was already resolved by t1312 (PR #2221), which removed the heartbeat/watchdog
code entirely from the active supervisor path before archiving.

Closes #3364

---------

Co-authored-by: alex-solovyev <1556417+alex-solovyev@users.noreply.github.com>
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.

t1312: Interactive brief generation with latent criteria probing

1 participant