CLI automation (orchestration) should not count as third-party harness

Problem

Starting April 4, third-party harnesses draw from extra usage instead of subscription. My project (ConfigHub.Orchestrator) is being classified as a third-party harness, but it simply spawns claude CLI processes — the exact same binary, same auth, same everything as running Claude Code manually in a terminal.

What my project does

It's a C#/.NET service that automates a GSD pipeline: Forgejo issues trigger phases (discuss, plan, execute), each phase spawns a standard claude CLI process. It's the equivalent of me having multiple terminal windows open running Claude Code manually — just with a task queue and state machine in front of it.

Why this classification is wrong

• It uses the official Claude Code CLI — not a reimplementation or alternative client
• It doesn't bypass any auth, rate limits, or protocols
• It's the same usage pattern as a human typing commands, just automated
• This is exactly what "build nice things on top of Claude Code" means

Ask

Please distinguish between alternative clients (like OpenClaw) and automation/orchestration layers that simply invoke the official claude CLI. Users who automate their own workflow shouldn't be penalized for building on top of your product.