You're offline — showing cached data

MC-4501

Follow-up: normalize omitted author_type behavior in ticket comments
2026-06-13 08:47:40 SAST
Home Board MC-4501

Follow-up: normalize omitted author_type behavior in ticket comments

Follow-up from MC-4500 final Opus review. The Control Room v2 flag-on path now requires explicit `author_type == "human"` (or trusted identity fill) before atomic Controller aud...
State Done Next Action Waiting: done Owner Luci Runtime Closed Age 13d ago
MC-4501
Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/state/control-room-worktrees/mc-4501-author-type · uptime 12d 11h · last activity 12d 11h ago

Description

MC-4501
Follow-up from MC-4500 final Opus review. The Control Room v2 flag-on path now requires explicit `author_type == "human"` (or trusted identity fill) before atomic Controller audit routing. However, the legacy fallback path still defaults omitted `author_type` to `"human"` in `models.add_comment(...)`, so an untrusted/API caller omitting author_type can create a human-typed comment without Controller audit when the flag is enabled. This is not release-blocking for MC-4500 because UI posts explicit human and trusted humans are identity-filled, but it should be cleaned up/documented before enabling the flag broadly. Acceptance: - Decide and implement canonical behavior for omitted author_type on ticket comments. - Preserve trusted human identity behavior. - Preserve worker/system comments. - Add tests for omitted author_type under flag-on and flag-off. - No runtime auto-dispatch regressions.

Activity

done
Luci is working...
Live
No activity yet
Help