+7
−1
Loading
resources/variables.py named `develop` in the context URL, so every run of every
fork - however carefully corrected - handed the broker UPSTREAM's context at
runtime. A change there altered what our tests mean with no commit on our side:
`isParked` was added to the upstream context, the broker started expanding it
correctly, and twelve expectation files that were written before that suddenly
disagreed. Nothing in our repository had moved.
The URL now names this branch. The compound context references its sibling
RELATIVELY, which is what makes the pair follow whichever branch serves it, so
this needed no other change - and the two context files, which until now were
carried but never used, are synced with develop so the behaviour is unchanged
today. Upstream's next context change arrives when we merge, deliberately, rather
than mid-run.
Also: 023_01_01's expectation expanded to match. It expects a read with NO
@context, where a term defined only in the suite context cannot compact and must
come back as an IRI - which the neighbouring entries in the same file already did.
Co-Authored-By:
Claude Opus 5 (1M context) <noreply@anthropic.com>