add-agent-adapterlisted

# Add an Agent adapter Implement adapter work without reading real user configuration during tests or allowing credential values into outputs. ## 1. Establish scope 1. Read `AGENTS.md`, `src/adapters/types.ts`, `src/adapters/index.ts`, and the closest existing adapter. 2. Confirm the Agent and configuration format are within the current product direction. 3. Decide separately which behavior belongs to discovery, parsing, rules, remediation, and baseline. 4. Prefer extending an existing adapter when the source and semantics are the same. ## 2. Preserve the adapter boundary - Implement `discover()` as a tolerant, read-only existence and location check. - Return `configFound: false` rather than throwing when an optional tool is absent. - Keep format parsing in `parse.ts`; normalize only fields required by findings. - Keep rule production in `risk.ts`; do not mix user-facing action semantics into parser code. - Register the adapter in `src/adapters/index.ts` and add its stable `AgentId` in `src/adapters/types.ts`. - Reuse `classifyBaseUrl` and project Provider policy instead of maintaining a private endpoint classifier. ## 3. Enforce privacy - Never return raw credential values from parse functions. - Represent secrets with existence, key names, counts, or the repository's irreversible fingerprint pattern. - Do not copy arbitrary config objects into evidence or exception messages. - Do not read the contents of credential-only files during discovery when existence is suffic