Decide: wire nousergon/mnemon into fleet groomer BACKLOG_REPOS — or keep interactive-only

[cipher813]

Decide: wire nousergon/mnemon into the fleet groomer's BACKLOG_REPOS — or keep mnemon interactive-only

Context (verified 2026-07-18)

The fleet groomer does NOT enumerate this repo: alpha-engine-config/scripts/groom_driver.py BACKLOG_REPOS (verified on origin/main) is exactly alpha-engine-config, metron-ops, vires-ops, telos-ops. So mnemon issues (e.g. #273/#274 from the claude.ai save-gap arc) are never picked up by the three daily groom triggers — they advance only when Brian works them in an interactive session. Surfaced when Brian asked "will mnemon issues be picked up by the groomer?" — decision was deferred at wind-down; this issue is the tracked record.

Decision required (operator: Brian)

• (a) Wire it in. Scope if yes:
  1. Add nousergon/mnemon to BACKLOG_REPOS in alpha-engine-config/scripts/groom_driver.py (and to CODE_REPOS if groom-opened mnemon PRs should be swept for accounting).
  2. Create complexity:low|mid|high labels on nousergon/mnemon (mirror alpha-engine-config colors) and label the ~28 open issues — the groomer's demand-driven tier dispatch keys on these; unlabeled ⇒ mid.
  3. Verify the scheduled-groom-dispatcher Lambda does not carry its own stale hardcoded copy of the repo list — this Lambda has drifted from repo source before (same bug class as alpha-engine-config-I2461's hardcoded WEEKLY_WET_CEILING).
  4. Accept the budget implication: mnemon (personal OSS) backlog then draws from the fleet's weekly WET usage pacing.
• (b) Keep mnemon out — interactive-session-only; close this issue with that ruling recorded.

Closes when

A comment records ruling (a) or (b); if (a), the three wiring steps above are shipped (groom_driver PR merged, labels applied, dispatcher Lambda list verified/fixed) and one groom decision-record shows mnemon enumerated.