Preserve deterministic counter runtime state

## Problem
The transformer materializes declarative counters directly to endpoint values while source visual capture observes their scripted runtime progression. Home therefore renders different values despite aligned section geometry.

## Direction
Define and preserve a deterministic counter presentation contract that matches source behavior at parity capture without fixture-specific values or timing hacks.

## Acceptance
- Home counter values and positions match source deterministically.
- Counter behavior remains useful in the imported site.
- Repeated captures are stable.
- Transformer contracts and parity fixtures pass.

## AI assistance
OpenAI gpt-5.6-sol through OpenCode analyzed the parity evidence and drafted this issue. Chris Huber remains responsible for scope and implementation decisions.

Start by tracing how the transformer materializes declarative counters and how source visual capture observes their scripted runtime progression. Use the transformer contracts and parity fixtures to compare Home values, positions, imported-site behavior, and repeated captures; done means the results match deterministically without fixture-specific values or timing hacks.

Written by the indexing model from the issue text.