Skip to content

Classify every spec as V1 or V2 before launch day #60

Description

@JarbasAl

Per VERSIONING.md (see the policy PR): V1 = formalization compatible with the V0 status quo (even if degraded); V2 = not backwards compatible. Every spec file and every open spec PR needs the classification added to its header. Candidate quick reads: parallel-namespace specs behind legacy_namespace gating → V1 with gated V2 sections; renames like fallback.ping/pong → V2 unless dual-emitted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions