Skip to content

Amend issue #8 acceptance criteria to reflect ADR-0013 + ADR-0014 #37

@JakeMG-INL

Description

@JakeMG-INL

Parent

#8

What to build

Rewrite issue #8's description and acceptance criteria in place to match the v1.0 public-surface state declared in ADR-0013 (packaging) and ADR-0014 (surface refinements). The original issue body references ADR-0003 (superseded by ADR-0012, then further by ADR-0014) and requires the README to mark V2Gjson/* as internal — directly contradicting the current authoritative ADR which makes V2Gjson public.

Replacement acceptance criteria should enumerate: 8 Namespaces covered, six-method Python API where supported, eight CLI binaries each with six modes where supported, V2Gjson public surface with naming-conventions note, typed exception attributes, pip-installable distribution, envelope-shape split documented per Namespace, CHANGELOG.md v1.0 entry, all round-trip suites green on main, v1.0 tag.

Do not close or fragment issue #8 — amend in place so the link from this conversation to the issue tracker history is preserved.

Acceptance criteria

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    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