open-claude-tag

Use ONLY with explicit user opt-in for a narrow, low-risk OpenClaudeTag repo change — docs/copy, static assets, a localized console UI tweak, a clearly isolated helper, or a localized test adjustment. Do focused verification and explicitly report which full gates you skipped. If the change turns out to touch any tier-2 area (schema, auth, queue/worker/runtime, Feishu events, daemon, secrets, deployment, or a broad refactor), stop and switch to self-dev.

Use when making a substantial change to the OpenClaudeTag repo itself (tier-2 blast radius — DB schema/migrations, storage/seed, auth/permissions/ownership, secrets, deployment/release, queue/worker/runtime adapters, Feishu event handling, daemon gateway, or a broad/architectural refactor). Confirm test cases plus an implementation plan, work test-first, pass the full gates, record ADRs on demand, and open a PR. For a narrow, low-risk change use fast-dev instead.

Use when making a substantial change to the OpenClaudeTag repo itself (tier-2 blast radius — DB schema/migrations, storage/seed, auth/permissions/ownership, secrets, deployment/release, queue/worker/runtime adapters, Feishu event handling, daemon gateway, or a broad/architectural refactor). Confirm test cases plus a technical approach, work test-first, pass the full gates, record ADRs on demand, and open a PR. For a narrow, low-risk change use fast-dev instead.