Skip to content

Sync table: classify every template↔suite pair #45

Description

@diegohb

Part of #44 — spec item 2.

Classify every mirrored template↔suite pair in one table (single place answering "are we in sync?"):

  • byte-synced — test asserts source equals template body. Widen enforcement to every pair whose bodies can genuinely be identical; at minimum assert the root entry pair that already matches but is unasserted.
  • declared-divergent — a divergence manifest names the policy: suite-only broad clear-cache modes and status path/package flags; generated-only migrate and both-scope status; suite installer is a class while the generated installer is function-style.
  • fixture-covered — generated-only files exercised by the rendered fixture.

Conformance checklist and publisher instructions reference the table instead of restating policy. Declared-divergent tests assert the policy difference itself, not just inequality.

Coordinates with #20 on the template test harness — land #20's renderer extraction first.

Tests: sync table asserting source == template body for byte-synced rows; asserting the policy difference for declared-divergent rows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions