Add pre-push verification and cross-surface update conventions

[kelos-bot]

/kind cleanup

What this PR does / why we need it:

Adds agent conventions based on recurring review feedback:

1. Run make verify and make test before pushing — Workers and PR-responder agents previously pushed code before running any local verification, causing preventable CI failures. Now verification is required before the initial push in both "new PR" and "existing PR" flows.

2. Update all related surfaces together — When changing user-facing guidance, agents must search for all surfaces (docs, CLI output, templates, code comments) that reference the same topic and update them together to avoid inconsistencies.

3. Provider-agnostic API design — When adding CRD fields or API types, prefer generic abstractions over provider-specific ones (e.g., none credential type instead of bedrock). Use existing generic mechanisms like PodOverrides.Env for provider-specific details.

4. Idiomatic Helm values — Use nested dictionary structures in values.yaml (e.g., controller.resources.requests.cpu) instead of flat string-based parameters. Structured data should be proper YAML dictionaries, not strings.

Evidence from PR reviews:

• Pre-push verification: PR Migrate install mechanism to embedded Helm chart templating #728 (gjkim42: "CI keeps failing. Check it and update the patches."), PR Remove duplicate root-level chart and CRD files #740 (gjkim42: "Fix the CI.") — multiple rounds of CI failures because agents pushed before verifying locally.
• Cross-surface consistency: PR Recommend claude setup-token for OAuth credentials #741 (gjkim42: "Is there any other places to update?") — agent updated README with claude setup-token guidance but missed updating the CLI init template.
• Provider-agnostic API design: PR feat: native IRSA auth #785 — reviewer required generic none credential type instead of AWS-specific bedrock, redirecting the contributor to use PodOverrides.Env for provider-specific details rather than adding dedicated CRD fields.
• Idiomatic Helm values: PR Add configurable resource requests/limits for the controller #783 — multiple review rounds corrected flat string-based Helm values to idiomatic nested dictionaries (controller.resources.requests|limits), and reviewer noted values should be proper YAML dicts, not empty strings.

Files changed:

• self-development/kelos-workers.yaml — Add verification step before push in both PR-exists (5a) and no-PR (new step 4b) flows
• self-development/kelos-pr-responder.yaml — Add verification before commit+push in step 5
• self-development/agentconfig.yaml — Add cross-surface consistency, provider-agnostic API, and Helm conventions
• AGENTS.md / CLAUDE.md — Add cross-surface consistency, provider-agnostic API, and Helm conventions

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

All new conventions are backed by specific PR review evidence. No speculative rules added.

Does this PR introduce a user-facing change?

NONE

[cubic-dev-ai]

No issues found across 4 files