[V3 Design] Technical Consistency Audit and Meta-Language Refinement

[Omswastik-11]

Summary

The V3 prototype API documents include language-specific syntax that leaks into the language-agnostic meta-language (for example Java-style primitive and collection types). This issue tracks normalization in keys, config, and common so the specs are implementation-neutral across Java, Go, Python, C++, Rust, Swift, JS/TS.

Problem

Current specs contain mixed conventions that conflict with the core guideline:

• Java-specific forms like byte array and boolean in keys API definitions
• Incorrect casing of primitive types
• Java collection syntax instead of meta-language collection syntax
• Type naming and reference inconsistencies in key format-related definitions

These inconsistencies can cause confusion during implementation and produce divergent SDK mappings.

Scope

• v3-sandbox/prototype-api/keys.md
• v3-sandbox/prototype-api/config.md
• v3-sandbox/prototype-api/common.md
• Reference guideline: guides/api-guideline.md

Proposed Changes

1. Normalize key API types to canonical meta-language primitives.
2. Replace language-specific collection syntax with canonical meta-language collection syntax.
3. Normalize primitive casing and naming consistency.
4. Clean up inconsistent key-format type references.

[Omswastik-11]

Hi @hendrikebbers !! Any thoughts on refinement ideas ? I would like to implement