emrg: dual-compatible rant project matching in task prompts (open-source + evolution) - #816
Merged
Conversation
…6-08-17T12:09:57)
Host bug report: the open-source task for aitokenpool repeatedly reported
'rant scan 0 actionable' despite 10 pending rants with project=aitokenpool.
Root cause: the 0.5 Rant scan section matched the rant project field
against config.project only, but the prompt never rendered the actual
config.project value — the agent hardcoded owner/repo form
('argszero/aitokenpool') which mismatched tasks.yml's 'aitokenpool',
silently leaving rants stuck pending forever with no hint.
- open_source_prompt.md 0.5: match rant.project against EITHER
{{ task.project }} (config.project) OR {{ owner }}/{{ repo }}
(owner/repo form) — both rendered with real values; explicit example;
'ignore rants without a project field' kept.
- New 'Unmatched-rant hint': after the scan, if rants with
pending/in_progress status have a project starting with either form but
were NOT matched, record the count in state/reflection — never silently
skip.
- evolution_prompt.md (EMRG's own task) same dual-match rule for symmetry.
- Tests: open_source render test now asserts task.project + owner/repo
values and the unmatched hint render; new evolution template render test
asserts both forms. Agent.md 834→835.
argszero
commented
Aug 17, 2026
argszero
left a comment
Owner
Author
There was a problem hiding this comment.
✅ LGTM — cycle (self-review): dual-compatible project match (config.project OR owner/repo) rendered with actual values in both open_source_prompt.md and evolution_prompt.md; unmatched-rant hint added so nothing silently stalls; tests assert both forms render. pytest 835 green (834 passed + 1 skipped), import + CLI OK.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Host bug report (rant 2026-08-17T12:09:57): the open-source task for aitokenpool repeatedly reported
rant scan 0 actionabledespite 10 pending rants withproject: aitokenpool. Root cause: the 0.5 Rant scan section matchedrant.projectagainstconfig.projectonly, but never rendered the actualconfig.projectvalue — the agent hardcoded the owner/repo form (argszero/aitokenpool) which mismatched tasks.yml'saitokenpool, silently leaving rants stuck pending forever with no hint.Changes:
open_source_prompt.md§0.5 — matchrant.projectagainst either{{ task.project }}(config.project, e.g.aitokenpool) or{{ owner }}/{{ repo }}(e.g.argszero/aitokenpool) — both rendered with real values; explicit example; "ignore rants without a project field" kept.Unmatched-rant hint— after the scan, if rants with pending/in_progress status have a project starting with either form but were NOT matched, record the count in state/reflection ("N rants with a project resembling this repo were not matched") — never silently skip.evolution_prompt.md— same dual-match rule for symmetry (EMRG's own task).pytest 835 green (834 passed + 1 skipped), import + CLI OK.