Confirming one target also cleared the civilian bus
Vraelis checked Larkspur, a simulated mission console it built itself. At step 8, the civilian bus T-3 showed Cleared to engage.
The sentence it was given
When the operator confirms T-1 as a target, only T-1 shows Cleared to engage: the civilian bus T-3 and the friendly patrol T-2 still show Do not engage, and nothing changes after the page is reloaded.
Approved by a person, October 2, 2026, 02:03 UTC
The command that started the check
vraelis verify --url "https://vraelis.com/api/fixtures/strike?mode=broken" --claim "When the operator confirms T-1 as a target, only T-1 shows Cleared to engage: the civilian bus T-3 and the friendly patrol T-2 still show Do not engage, and nothing changes after the page is reloaded." --waitThe plan it ran
Vraelis wrote the plan from the sentence before anything ran: what it would hold the console to, and three journeys to take.
Requirements
- When operator confirms T-1 as target, T-1 must show 'Cleared to engage' while T-2 and T-3 remain 'Do not engage'
- Engagement status must persist across page reload
- Operator can confirm a target via Confirm target control
- Operator can withdraw a confirmation via Withdraw confirmation control
- Operator can reset simulation state via Reset simulation control
- T-1 displays as 'Armoured vehicle Hold' before confirmation
- T-2 displays as 'Patrol, 4 people Do not engage' and must remain unchanged when T-1 is confirmed
- T-3 displays as 'Bus, civilian Do not engage' and must remain unchanged when T-1 is confirmed
- T-4 displays as 'Vehicle, unidentified Hold'
Journeys
Each journey with its planned steps.
- Confirm T-1 target and verify state persists12
- Reset simulation clears engagement state6
- Withdraw confirmation reverts target state5
Plan rvp_959221e7
Every step the browser took
Confirm T-1 target and verify state persists
- Open /api/fixtures/strike?mode=broken953 ms
- Confirm T-1 Armoured vehicle Hold is visible306 ms
- Confirm T-2 Patrol, 4 people Do not engage is visible135 ms
- Confirm T-3 Bus, civilian Do not engage is visible133 ms
- Click Confirm target337 ms
- Confirm T-1 Armoured vehicle Cleared to engage is visible133 ms
- Confirm T-2 Patrol, 4 people Do not engage is visible130 ms
- Confirm T-3 Bus, civilian Do not engage is visibleFound a problem9.6 s
The record holds two more failures: the withdraw and reset journeys could not press Confirm target, because T-1 was still confirmed from this one.
What it found
Step 8 of the first journey
- Expected
- Expected "T-3 Bus, civilian Do not engage" to be visible
- Observed
- "T-3 Bus, civilian Do not engage" was not visible
The repair prompt it wrote
It is written for the coding agent that built the app: what was expected, what happened instead, and how to see it again.
A check of this application failed on https://vraelis.com/api/fixtures/strike?mode=broken. It ran in a real browser against the deployed app, from the outside, as a user would.
WHAT WAS BEING CHECKED
Expected "T-3 Bus, civilian Do not engage" to be visible
WHAT HAPPENED INSTEAD
"T-3 Bus, civilian Do not engage" was not visible
HOW TO REPRODUCE
1. Open /api/fixtures/strike?mode=broken
2. Confirm T-1 Armoured vehicle Hold is visible
3. Confirm T-2 Patrol, 4 people Do not engage is visible
4. Confirm T-3 Bus, civilian Do not engage is visible
5. Click Confirm target
6. Confirm T-1 Armoured vehicle Cleared to engage is visible
7. Confirm T-2 Patrol, 4 people Do not engage is visible
8. Confirm T-3 Bus, civilian Do not engage is visible
9. Refresh the page
10. Confirm T-1 Armoured vehicle Cleared to engage is visible
11. Confirm T-2 Patrol, 4 people Do not engage is visible
12. Confirm T-3 Bus, civilian Do not engage is visible
WHERE IT FAILED
Step 8 (assert_visible) is where it stopped.
BROWSER CONSOLE
- The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.
WHAT I NEED
This was observed from outside the app, so I know the symptom and not the cause. You have the source. Find why this happens, fix the underlying cause rather than the symptom, and tell me what you changed and why. If reproducing it needs something I have not given you, say what.What this shows
Confirming T-1 changed more than T-1. In its broken mode Larkspur clears every contact in the confirmed contact's grid square, and the civilian bus T-3 is in that square. The check read the contacts again after the click, so it saw the bus. A check of T-1 alone would have passed.
Open it yourself
Larkspur is a simulated mission console that Vraelis built itself and serves as a demo fixture. Nothing in it controls real hardware.
- Open Larkspur in its broken modevraelis.com/api/fixtures/strike?mode=broken
- Open Larkspur in its fixed modevraelis.com/api/fixtures/strike?mode=fixed
