emrg: open-source rant project match — single config.project value (drop dual-compat) - #821
Conversation
… (rant 2026-08-17T14:17:03)
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle 576: open_source 0.5 now matches the single config.project value, owner/repo explicitly non-matching, unmatched-hint kept; template test updated; CI test+test-windows green. Matches rant 2026-08-17T14:17:03.
|
I tested this PR end-to-end (Windows, branch feature/os-rant-single-project):
The single-value semantics are clearer than the dual-compat form: with |
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle 577: re-verified diff (open_source_prompt.md single-match + test update); CI green, mergeable CLEAN; pm25coder Windows pass confirms. 2/3.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle 578: 3rd consecutive approval (576/577/578). Re-verified: single-match semantics correct, tests green, CI pass, mergeable CLEAN. Merging.
Fix host rant 2026-08-17T14:17:03 — host decision: rant project matching must use the SINGLE value
config.project, no dual-compat.Background: PR #760/#816 introduced owner/repo dual-compat matching, but the host ruled it out — rants should carry the
config.projectvalue (e.g.aitokenpool), and scanning matches only that one value.Changes (emrg/server/open_source_prompt.md 0.5 Rant scan):
projectagainst exactly{{ task.project }}(config.project); owner/repo form ({{ owner }}/{{ repo }}) no longer matchesaitokenpool→project: aitokenpoolmatches;project: argszero/aitokenpooldoes NOT matchTests: test_scheduler.py open_source template test updated to assert the single-match rule renders ("does NOT match" present).
Note: this changes the template only — installed runtime (v0.2.42) picks it up on the host's next update.