chore: adopt dev standards 1.1.0

[krav01]

Summary

• adopt krav01/dev-standards baseline 1.1.0
• classify the project as high-load-critical
• preserve the existing stronger local verification pipeline
• record applicable controls and explicit exceptions

Reasoning

Chosen approach

Adopt the shared baseline through .standards.yml and a project-local adoption note without replacing current workflows.

Alternatives considered

• Replace local verification with the generic reusable Go CI.
• Copy shared workflows into this repository.

Why rejected/deferred

The existing project verification is substantially stronger and includes PostgreSQL integration, migration round-trip, Docker smoke, outage/recovery, backup/restore, schema upgrade, benchmark artifacts, CodeQL, Dependency Review, and Dependabot. Also, this repository is public while dev-standards is private, so public-to-private reusable workflow calls are not available.

Risk accepted

Standards drift remains manual for this public repository until the visibility/access model changes.

Revisit trigger

Enable reusable CI/drift checks if repository visibility changes or the shared workflow source becomes accessible to public callers.

Verification

• diff contains only .standards.yml and docs/standards-adoption.md
• production code and existing workflows are unchanged
• stronger local controls are preserved