Skip to content

Add explicit metadata for synthetic-only fixture assumptions #64

Description

@knytcomics-ui

Category

Good First

Summary

Add and validate a per-destination field distinguishing synthetic-only fixtures from any future network-visible fixture.

Current Behavior

Synthetic and unfunded status is documented globally, not recorded per entry.

Problem

Future contributors can add entries with different lifecycle assumptions without recording them explicitly.

Why This Matters

Per-fixture status prevents consumers from treating synthetic labels as live Horizon truth.

Proposed Scope

Add a constrained field such as fixture_status: "synthetic-only", populate current entries, and validate allowed values.

Acceptance Criteria

  • Every destination has an explicit status.
  • Missing or unknown statuses fail validation.
  • Existing fixtures are marked consistently.
  • The consumer contract remains compatible.
  • CONTRIBUTING.md documents the field.

Technical Considerations

The field is additive; coordinate with the vendored adapter schema before release.

Testing Requirements

Cover missing, invalid, and valid status values.

Cross-Repository Impact

Adapter fixture schema compatibility must be checked.

Out of Scope

Do not perform Horizon lookups; see issue #44.

Complexity

Localized schema and documentation change.

Impact

Medium — improves data safety.

Suggested Labels

good first issue, area: fixtures, area: validation

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third Campaignarea: fixturesDestination and transaction fixture coveragearea: validationFixture schema and integrity checksenhancementNew feature or requestgood first issueGood for newcomers

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions