internal/app/archied/bootstrap.go:1361-1364 iterates cfg.Curators and does 'if !def.Enabled { continue }' with no log and no counter, so a curator definition that is present but not enabled disappears without a trace. internal/infrastructure/configuration/validate.go validateCurators only rejects a definition whose interval is <= 0 (validate.go:144-152); it never mentions Enabled, so a disabled entry is never distinguished from a typo'd or misspelled definition. The AGENTS.md trap applies: the key parses, appears in config, and does nothing. Suggested fix: log at Info (or Debug) when a definition is skipped for being disabled, so an operator can tell 'deliberately off' from 'I misspelled the section'. The dashboard/config-schema surface is separate and already carried by archie-core-trnd.3, so this bead is only the silent-skip observability gap. Found during the 2026-10-02 triage of archie-core-trnd.1 (whose Phase-1 engine work is shipped).
Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads archie-core-d0jp · GitHub #1334 · type task · priority P2 · created 2026-10-02 · closed 2026-10-17
internal/app/archied/bootstrap.go:1361-1364 iterates cfg.Curators and does 'if !def.Enabled { continue }' with no log and no counter, so a curator definition that is present but not enabled disappears without a trace. internal/infrastructure/configuration/validate.go validateCurators only rejects a definition whose interval is <= 0 (validate.go:144-152); it never mentions Enabled, so a disabled entry is never distinguished from a typo'd or misspelled definition. The AGENTS.md trap applies: the key parses, appears in config, and does nothing. Suggested fix: log at Info (or Debug) when a definition is skipped for being disabled, so an operator can tell 'deliberately off' from 'I misspelled the section'. The dashboard/config-schema surface is separate and already carried by archie-core-trnd.3, so this bead is only the silent-skip observability gap. Found during the 2026-10-02 triage of archie-core-trnd.1 (whose Phase-1 engine work is shipped).
### Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
---
_Imported from beads `archie-core-d0jp` · GitHub #1334 · type task · priority P2 · created 2026-10-02 · closed 2026-10-17_
sam
added the mediumtask labels 2026-10-27 13:39:44 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
internal/app/archied/bootstrap.go:1361-1364 iterates cfg.Curators and does 'if !def.Enabled { continue }' with no log and no counter, so a curator definition that is present but not enabled disappears without a trace. internal/infrastructure/configuration/validate.go validateCurators only rejects a definition whose interval is <= 0 (validate.go:144-152); it never mentions Enabled, so a disabled entry is never distinguished from a typo'd or misspelled definition. The AGENTS.md trap applies: the key parses, appears in config, and does nothing. Suggested fix: log at Info (or Debug) when a definition is skipped for being disabled, so an operator can tell 'deliberately off' from 'I misspelled the section'. The dashboard/config-schema surface is separate and already carried by archie-core-trnd.3, so this bead is only the silent-skip observability gap. Found during the 2026-10-02 triage of archie-core-trnd.1 (whose Phase-1 engine work is shipped).
Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads
archie-core-d0jp· GitHub #1334 · type task · priority P2 · created 2026-10-02 · closed 2026-10-17