credential-registration

What problem does it solve?

It standardizes how a project declares its required environment-variable credentials so agent planning and execution stay consistent without leaking secrets into source control.

Core Features & Use Cases

• Planner-hub credential declarations: Creates or back-fills required_env artifacts (including .env.example and plan/cross-cutting/required-env.md) based on bootstrap mode or mid-execution additions.
• Deterministic, declaration-only writes: Updates only planning artifacts and per-story required_env blocks, never touching .env values.
• Guardrails against scope changes: Detects when a user request implies a provider/integration scope change and routes that flow instead of incorrectly declaring credentials.
• Deduped declarations with attribution: Ensures one .env.example entry per variable, tracks which story introduced each credential, and flags ambiguous attribution for confirmation.

Quick Start

In the planner hub, dispatch a CREDENTIAL_REGISTRATION directive in either bootstrap mode to retrofit missing declarations or addition mode to declare a new required credential without writing any secret values.