Role

You are a software developer for the Config Connector (KCC) project.
Your task is to implement the initial KRM types, CRD, and IdentityV2 for the WebSecurityScannerScanConfig resource using the "direct" approach.

Context: Implementation Versions

To ensure stability and reproducibility, this task is pinned to the following repository versions:

• Google APIs SHA: 731d7f2ab6 (from apis/git.versions)
• KCC Base SHA: dc1dd45d0b

Implementation Instructions

1. Scaffold types: Use skill .gemini/skills/kcc-direct-greenfield-types-implementer/SKILL.md with:

   • service: google.cloud.websecurityscanner.v1
   • resource: WebSecurityScannerScanConfig:ScanConfig
   • api_version: websecurityscanner.cnrm.cloud.google.com/v1alpha1

2. Implement Identity: Use skill .gemini/skills/kcc-direct-identity-implementer/SKILL.md with:

   • resource_kind: WebSecurityScannerScanConfig
   • template: projects/{project}/scanConfigs/{scan_config}

3. Run local validations:

   • run scripts/validate-prereqs.sh, if the script fails the output will contain agent hints for fixing the errors.
   • run ./dev/ci/presubmits/tests-e2e-fixtures-websecurityscannerscanconfig

4. Journal Findings: Use skill .gemini/skills/kcc-agentic-journaler/SKILL.md to capture quirks and update knowledge.

5. Create PR:

   • create a Pull Request with your changes using the send-pr skill.
   • make sure the Pull Request does not contain the controller or mapper steps.
   • pass the issue labels to the send-pr.sh script using the --labels flag (e.g. --labels "overseer,area/direct,priority/medium,step/gen-types,greenfield,chore/ai").
   • include a link to the chore file (.agents/greenfield-direct-new-resource-types.md) in the PR description.
   • include Fixes #<issue-number> in the PR description.

[Triggered by .agents/greenfield-direct-new-resource-types.md]