Skip to content

fix: Prevent short tokens from matching keywords via prefix#735

Merged
stranske merged 2 commits intomainfrom
fix/keyword-matcher-short-token-prefix
Jan 10, 2026
Merged

fix: Prevent short tokens from matching keywords via prefix#735
stranske merged 2 commits intomainfrom
fix/keyword-matcher-short-token-prefix

Conversation

@stranske
Copy link
Copy Markdown
Owner

@stranske stranske commented Jan 10, 2026

Source: Issue #123

Automated Status Summary

Scope

After merging PR #103 (multi-agent routing infrastructure), we need to:

  1. Validate the CLI agent pipeline works end-to-end with the new task-focused prompts
  2. Add GITHUB_STEP_SUMMARY output so iteration results are visible in the Actions UI
  3. Streamline the Automated Status Summary to reduce clutter when using CLI agents
  4. Clean up comment patterns to avoid a mix of old UI-agent and new CLI-agent comments

Context for Agent

Design Decisions & Constraints

    1. Clean up comment patterns to avoid a mix of old UI-agent and new CLI-agent comments
  • The keepalive loop now:
  • | <!-- keepalive-loop-summary --> | github-actions[bot] | NEW: CLI agent iteration tracking | ✅ Keep for CLI agents |
  • | <!-- keepalive-state:v1 --> | agents-workflows-bot[bot] | State tracking | ⚠️ Multiple copies accumulate |
  • | <!-- keepalive-round: N --> | stranske | OLD: Instruction comment | ❌ CLI agents dont need this |
  • The goal: For CLI agents (agent:* label), we should have exactly one updating comment (<!-- keepalive-loop-summary -->) instead of accumulating 10+ comments per PR.
  • Requires PR #103 to be merged first
  • This round you MUST:
  • Review the Scope/Tasks/Acceptance below, identify the next incomplete task that requires code, implement it, then post a reply comment with the completed items using their exact original text.

Related Issues/PRs

References

Blockers & Dependencies

  • After merging PR #103 (multi-agent routing infrastructure), we need to:
    1. Mark a task checkbox complete ONLY after verifying the implementation works.

Tasks

Pipeline Validation

  • After PR chore(codex): bootstrap PR for issue #101 #103 merges, create a test PR with agent:codex label
  • Verify task appendix appears in Codex prompt (check workflow logs)
  • Verify Codex works on actual tasks (not random infrastructure work)
  • Verify keepalive comment updates with iteration progress

GITHUB_STEP_SUMMARY

  • Add step summary output to agents-keepalive-loop.yml after agent run
  • Include: iteration number, tasks completed, files changed, outcome
  • Ensure summary is visible in workflow run UI

Conditional Status Summary

  • Modify buildStatusBlock() in agents_pr_meta_update_body.js to accept agentType parameter
  • When agentType is set (CLI agent): hide workflow table, hide head SHA/required checks
  • Keep Scope/Tasks/Acceptance checkboxes for all cases
  • Pass agent type from workflow to the update_body job

Comment Pattern Cleanup

  • For CLI agents (agent:* label):
  • Suppress <!-- gate-summary: --> comment posting (use step summary instead)
  • Suppress <!-- keepalive-round: N --> instruction comments (task appendix replaces this)
  • Update <!-- keepalive-loop-summary --> to be the single source of truth
  • Ensure state marker is embedded in the summary comment (not separate)
  • For UI Codex (no agent:* label):
  • Keep existing comment patterns (instruction comments, connector bot reports)
  • Keep <!-- gate-summary: --> comment
  • Add agent_type output to detect job so downstream workflows know the mode
  • Update agents-pr-meta.yml to conditionally skip gate summary for CLI agent PRs

Acceptance criteria

  • CLI agent receives explicit tasks in prompt and works on them
  • Iteration results visible in Actions workflow run summary
  • PR body shows checkboxes but not workflow clutter when using CLI agents
  • UI Codex path (no agent label) continues to show full status summary
  • CLI agent PRs have ≤3 bot comments total (summary, one per iteration update) instead of 10+
  • State tracking is consolidated in the summary comment, not scattered

Dependencies

Head SHA: 9be18ab
Latest Runs: ❔ in progress — Gate
Required: gate: ❔ in progress

Workflow / Job Result Logs
Agents PR meta manager ❔ in progress View run
CI Autofix Loop ✅ success View run
Gate ❔ in progress View run
Health 40 Sweep ✅ success View run
Health 44 Gate Branch Protection ✅ success View run
Health 45 Agents Guard ✅ success View run
Health 50 Security Scan ✅ success View run
Maint 52 Validate Workflows ✅ success View run
PR 11 - Minimal invariant CI ✅ success View run
Selftest CI ✅ success View run

The _token_matches_keyword function was allowing single-character
tokens to match keywords via prefix matching. For example:
- 'd' (from 'Describe') matched 'defect'
- 'a' could match 'add'

This caused feature requests to get 'bug' label (0.91) because
typical issue text contains short tokens that prefix-match bug
keywords.

Fix: Require token to be >= 4 chars before allowing prefix matching
in either direction.

Before: token='d', keyword='defect' → True (defect.startswith('d'))
After:  token='d', keyword='defect' → False (len('d') < 4)
Copilot AI review requested due to automatic review settings January 10, 2026 04:11
@github-actions github-actions bot added the autofix Opt-in automated formatting & lint remediation label Jan 10, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 10, 2026

Status | ✅ no new diagnostics
History points | 1
Timestamp | 2026-01-10 04:19:37 UTC
Report artifact | autofix-report-pr-735
Remaining | 0
New | 0
No additional artifacts

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 10, 2026

Automated Status Summary

Head SHA: b413caf
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / Enforce agents workflow protections
Required: core tests (3.11): ⏳ pending, core tests (3.12): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job Result Logs
(no jobs reported) ⏳ pending

Coverage Overview

  • Coverage history entries: 1

Coverage Trend

Metric Value
Current 92.21%
Baseline 85.00%
Delta +7.21%
Minimum 70.00%
Status ✅ Pass

Top Coverage Hotspots (lowest coverage)

File Coverage Missing
scripts/workflow_health_check.py 62.6% 28
scripts/classify_test_failures.py 62.9% 37
scripts/ledger_validate.py 65.3% 63
scripts/mypy_return_autofix.py 82.6% 11
scripts/ledger_migrate_base.py 85.5% 13
scripts/fix_cosmetic_aggregate.py 92.3% 1
scripts/coverage_history_append.py 92.8% 2
scripts/workflow_validator.py 93.3% 4
scripts/update_autofix_expectations.py 93.9% 1
scripts/pr_metrics_tracker.py 95.7% 3
scripts/generate_residual_trend.py 96.6% 1
scripts/build_autofix_pr_comment.py 97.0% 2
scripts/aggregate_agent_metrics.py 97.2% 0
scripts/fix_numpy_asserts.py 98.1% 0
scripts/sync_test_dependencies.py 98.3% 1

Updated automatically; will refresh on subsequent CI/Docker completions.


Keepalive checklist

Scope

After merging PR #103 (multi-agent routing infrastructure), we need to:

  1. Validate the CLI agent pipeline works end-to-end with the new task-focused prompts
  2. Add GITHUB_STEP_SUMMARY output so iteration results are visible in the Actions UI
  3. Streamline the Automated Status Summary to reduce clutter when using CLI agents
  4. Clean up comment patterns to avoid a mix of old UI-agent and new CLI-agent comments

Context for Agent

Design Decisions & Constraints

    1. Clean up comment patterns to avoid a mix of old UI-agent and new CLI-agent comments
  • The keepalive loop now:
  • | <!-- keepalive-loop-summary --> | github-actions[bot] | NEW: CLI agent iteration tracking | ✅ Keep for CLI agents |
  • | <!-- keepalive-state:v1 --> | agents-workflows-bot[bot] | State tracking | ⚠️ Multiple copies accumulate |
  • | <!-- keepalive-round: N --> | stranske | OLD: Instruction comment | ❌ CLI agents dont need this |
  • The goal: For CLI agents (agent:* label), we should have exactly one updating comment (<!-- keepalive-loop-summary -->) instead of accumulating 10+ comments per PR.
  • Requires PR #103 to be merged first
  • This round you MUST:
  • Review the Scope/Tasks/Acceptance below, identify the next incomplete task that requires code, implement it, then post a reply comment with the completed items using their exact original text.

Related Issues/PRs

References

Blockers & Dependencies

  • After merging PR #103 (multi-agent routing infrastructure), we need to:
    1. Mark a task checkbox complete ONLY after verifying the implementation works.

Tasks

Pipeline Validation

  • After PR chore(codex): bootstrap PR for issue #101 #103 merges, create a test PR with agent:codex label
  • Verify task appendix appears in Codex prompt (check workflow logs)
  • Verify Codex works on actual tasks (not random infrastructure work)
  • Verify keepalive comment updates with iteration progress

GITHUB_STEP_SUMMARY

  • Add step summary output to agents-keepalive-loop.yml after agent run
  • Include: iteration number, tasks completed, files changed, outcome
  • Ensure summary is visible in workflow run UI

Conditional Status Summary

  • Modify buildStatusBlock() in agents_pr_meta_update_body.js to accept agentType parameter
  • When agentType is set (CLI agent): hide workflow table, hide head SHA/required checks
  • Keep Scope/Tasks/Acceptance checkboxes for all cases
  • Pass agent type from workflow to the update_body job

Comment Pattern Cleanup

  • For CLI agents (agent:* label):
  • Suppress <!-- gate-summary: --> comment posting (use step summary instead)
  • Suppress <!-- keepalive-round: N --> instruction comments (task appendix replaces this)
  • Update <!-- keepalive-loop-summary --> to be the single source of truth
  • Ensure state marker is embedded in the summary comment (not separate)
  • For UI Codex (no agent:* label):
  • Keep existing comment patterns (instruction comments, connector bot reports)
  • Keep <!-- gate-summary: --> comment
  • Add agent_type output to detect job so downstream workflows know the mode
  • Update agents-pr-meta.yml to conditionally skip gate summary for CLI agent PRs

Acceptance criteria

  • CLI agent receives explicit tasks in prompt and works on them
  • Iteration results visible in Actions workflow run summary
  • PR body shows checkboxes but not workflow clutter when using CLI agents
  • UI Codex path (no agent label) continues to show full status summary
  • CLI agent PRs have ≤3 bot comments total (summary, one per iteration update) instead of 10+
  • State tracking is consolidated in the summary comment, not scattered

Dependencies

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 10, 2026

🤖 Keepalive Loop Status

PR #735 | Agent: Codex | Iteration 0/5

Current State

Metric Value
Iteration progress [----------] 0/5
Action wait (missing-agent-label)
Disposition skipped (transient)
Gate success
Tasks 0/28 complete
Keepalive ❌ disabled
Autofix ❌ disabled

🔍 Failure Classification

| Error type | infrastructure |
| Error category | resource |
| Suggested recovery | Confirm the referenced resource exists (repo, PR, branch, workflow, or file). |

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a bug where short tokens (< 4 characters) from issue text were incorrectly matching keywords via prefix matching, causing issues to receive incorrect labels. The fix adds a length requirement (>= 4 chars) to prevent short tokens like "d" (from "Describe") from matching keywords like "defect".

Changes:

  • Modified _token_matches_keyword to require tokens be at least 4 characters long before allowing prefix matching
  • Added inline comments explaining the rationale for the 4-character minimum

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 324 to +332
def _token_matches_keyword(token: str, keyword: str) -> bool:
if token == keyword:
return True
# Only allow prefix matching for tokens >= 4 chars to avoid false positives
# from short tokens like "d" matching "defect" or "a" matching "add"
if len(token) >= 4 and token.startswith(keyword):
return True
return bool(len(keyword) >= 4 and keyword.startswith(token))
# Check if keyword starts with token (both must be >= 4 chars)
return len(token) >= 4 and len(keyword) >= 4 and keyword.startswith(token)
Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

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

The fix correctly prevents short tokens from matching keywords via prefix. However, there's no test coverage for this specific scenario. Consider adding a test case that verifies tokens shorter than 4 characters (e.g., "d" from "Describe") do not match keywords like "defect", which was the root cause of the bug described in the PR.

Copilot uses AI. Check for mistakes.
@stranske stranske enabled auto-merge (squash) January 10, 2026 04:15
@stranske stranske merged commit aa61bd1 into main Jan 10, 2026
99 checks passed
@stranske stranske deleted the fix/keyword-matcher-short-token-prefix branch January 10, 2026 04:20
stranske added a commit that referenced this pull request Jan 10, 2026
…results

- Document PRs #733, #735 (deep label matcher fixes)
- Record validation test results (issues #265-267)
- Mark auto-label validation as complete
- Key win: 2FA feature request now gets only 'enhancement' (was 3 labels)
stranske added a commit that referenced this pull request Jan 10, 2026
* docs: Update SHORT_TERM_PLAN with label matcher fixes and validation results

- Document PRs #733, #735 (deep label matcher fixes)
- Record validation test results (issues #265-267)
- Mark auto-label validation as complete
- Key win: 2FA feature request now gets only 'enhancement' (was 3 labels)

* docs: Add LONG_TERM_PLAN for Phases 4-5

- Phase 4: Auto-pilot workflow, user guide, conflict resolution
- Phase 5: Learning from feedback, multi-model arbitration
- Infrastructure: Performance, monitoring, cost optimization
- Risk assessment and success metrics
- Prioritized 8-week roadmap
stranske added a commit that referenced this pull request Jan 10, 2026
* docs: Update SHORT_TERM_PLAN with label matcher fixes and validation results

- Document PRs #733, #735 (deep label matcher fixes)
- Record validation test results (issues #265-267)
- Mark auto-label validation as complete
- Key win: 2FA feature request now gets only 'enhancement' (was 3 labels)

* docs: Add LONG_TERM_PLAN for Phases 4-5

- Phase 4: Auto-pilot workflow, user guide, conflict resolution
- Phase 5: Learning from feedback, multi-model arbitration
- Infrastructure: Performance, monitoring, cost optimization
- Risk assessment and success metrics
- Prioritized 8-week roadmap

* Expand cleanup_labels.py classifications

- Add autofix:*, integration-*, agents:keepalive-nudge to functional
- Add common component labels (app, engine, ui, backend, cli)
- Add tech labels (javascript, python, github:actions)
- Add domain labels (metrics, modeling, schema, etc.)
- Reduces idiosyncratic labels from 150+ to 24
- Remaining 24 are legitimate project-specific labels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autofix Opt-in automated formatting & lint remediation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants