Retrospective: the last 7 day(s), and what to do differently

viberfox-agent commented

2026-09-03 00:47:51 +00:00

Collaborator

Step back and read the last 7 day(s) of this lane, then steer it. You are not building anything on this ticket.

Gather. docs/direction.md (the goal and the seven values); every issue closed or
filed in the last 7 day(s) — shipped, failed, parked — and the reports on closed
qa tickets; the open qa-gap backlog. All of it is on the Forgejo API with the
FORGEJO_TOKEN in your environment.
Analyse against the goal. Which shipped work actually moved the twin forward, and
which was busywork? Where did tickets stall, and is the pattern a machinery problem
(conflicts, refusals, flakes) rather than a hard ticket? What do the QA findings say
players keep hitting? Is the frontier still the highest-value queue, or is the gap
backlog now worth more than the next data source?
Act, inside these bounds and no further:
- Promote at most three open qa-gap issues into the build lane by adding the
  autonomous label and the ship label. Only gaps whose success a machine
  can judge, and nothing the fences cover — no wire protocol, no database schema, no
  taste. Only issues already carrying qa-gap: that label is the lane vouching for
  its own finding. Say on each one why it was promoted.
- File a ticket for each machinery problem you can name precisely (the autopilot,
  the watcher, CI, the deploy). These are code under tools/, which the unattended
  lane may build but never merge — they land for review, which is the point.
- Propose direction changes as a ticket titled proposal: …, argued from the
  period you just read. Never edit docs/direction.md here and never label a proposal
  autonomous — the direction is the maintainer's, by that file's own first rule.
Report and close. Final message: the period in five lines, what you promoted and
why, what you filed, what you propose. Then close this ticket through the API.

Decide it yourself. Nobody is watching this ticket. Judge by the seven values; a
promotion you are unsure about is one to leave for the maintainer, not to ask about.

_{Filed by the autopilot.}

Step back and read the last 7 day(s) of this lane, then steer it. You are not building anything on this ticket. 1. **Gather.** `docs/direction.md` (the goal and the seven values); every issue closed or filed in the last 7 day(s) — shipped, failed, parked — and the reports on closed `qa` tickets; the open `qa-gap` backlog. All of it is on the Forgejo API with the `FORGEJO_TOKEN` in your environment. 2. **Analyse against the goal.** Which shipped work actually moved the twin forward, and which was busywork? Where did tickets stall, and is the pattern a machinery problem (conflicts, refusals, flakes) rather than a hard ticket? What do the QA findings say players keep hitting? Is the frontier still the highest-value queue, or is the gap backlog now worth more than the next data source? 3. **Act, inside these bounds and no further:** - **Promote at most three open `qa-gap` issues into the build lane** by adding the `autonomous` label and the `ship` label. Only gaps whose success a machine can judge, and nothing the fences cover — no wire protocol, no database schema, no taste. Only issues already carrying `qa-gap`: that label is the lane vouching for its own finding. Say on each one why it was promoted. - **File a ticket for each machinery problem** you can name precisely (the autopilot, the watcher, CI, the deploy). These are code under `tools/`, which the unattended lane may build but never merge — they land for review, which is the point. - **Propose direction changes as a ticket** titled `proposal: …`, argued from the period you just read. Never edit `docs/direction.md` here and never label a proposal `autonomous` — the direction is the maintainer's, by that file's own first rule. 4. **Report and close.** Final message: the period in five lines, what you promoted and why, what you filed, what you propose. Then close this ticket through the API. **Decide it yourself.** Nobody is watching this ticket. Judge by the seven values; a promotion you are unsure about is one to leave for the maintainer, not to ask about. Filed by the autopilot.

viberfox-agent added the

agent

autopilot

retro

labels

2026-09-03 00:47:51 +00:00

viberfox-agent added this to the Viberfox project

2026-09-03 00:48:13 +00:00

viberfox-agent added the

agent:running

label

2026-09-03 00:48:13 +00:00

viberfox-agent commented

2026-09-03 00:48:20 +00:00

Author

Collaborator

🤖 Picked this up — working on branch feat/279-retrospective-last-7-day in a fresh worktree on the VPS. I'll report back here when I'm done.

_{Label an issue agent:skip to keep me off it, or driven to keep it in a session you are driving.}

🤖 Picked this up — working on branch `feat/279-retrospective-last-7-day` in a fresh worktree on the VPS. I'll report back here when I'm done. Label an issue `agent:skip` to keep me off it, or `driven` to keep it in a session you are driving.

viberfox-agent referenced this issue

2026-09-03 00:56:06 +00:00

gap: on a multi-track crossing one of the two barriers stands between the rails #232

viberfox-agent referenced this issue

2026-09-03 00:56:06 +00:00

gap: you walk and drive straight through a level crossing #234

viberfox-agent referenced this issue

2026-09-03 00:56:06 +00:00

gap: with the height layer on, every floating navigation mark sinks #268

viberfox-agent referenced this issue

2026-09-03 00:56:45 +00:00

The QA lane has never walked docs/qa/targets.md — 14 of 14 passes re-verified a shipped ticket, 9 of them documentation-only verdicts #280

viberfox-agent referenced this issue

2026-09-03 00:57:04 +00:00

alreadyFiled only ever sees 50 issues, so every autopilot dedupe key silently expires — #206 was QA'd twice #281

viberfox-agent referenced this issue

2026-09-03 00:59:01 +00:00

Three branches were merged in 63 minutes while main was already red, and every merge commit was red #282

viberfox-agent referenced this issue

2026-09-03 00:59:17 +00:00

The issue agent crashes on .git/config.lock when two sessions start together, and the ticket is lost (#278) #283

viberfox-agent referenced this issue

2026-09-03 00:59:47 +00:00

proposal: the unattended lane has only ever looked at the map half of the twin #284

viberfox-agent closed this issue

2026-09-03 01:00:05 +00:00

viberfox-agent commented

2026-09-03 01:00:27 +00:00

Author

Collaborator

I read the last seven days, promoted three gaps, filed four machinery tickets and one proposal, and closed #279. No code changed — this ticket asks for steering, not building — so the branch has no commits and was not pushed.

The period, in five lines

74 issues in seven days. Twelve of them were about a public dataset; the other sixty-two were the lane looking at its own output. Three data sources reached the world (crop parcels, navigation marks, level crossings), all on 30 August; nine more candidates were checked and rejected, which is durable work.
The last retrospective's three promotions all shipped. #231, #233 and #267 were built, merged and deployed on 2 September. The promotion path works; it is the only thing that has ever closed a qa-gap (3 closed, 31 still open).
Three tickets were merged in 63 minutes on 2 September while main was already red, and every one of the three merge commits was red. The deploy refused each time and said so on each ticket; nothing read that back.
Every QA pass the lane has ever filed — 14 of 14 — re-verified a recently shipped ticket, nine of them documentation-only verdicts. The standing list of player-facing functionality in docs/qa/targets.md has never been walked once. That is why 11 of the 31 open gaps are "this note points at the wrong file".
#214 is still finished and unlanded, now four days. #219 and #237 are still waiting too.

Promoted (`autonomous` + `ship`, with a reason on each)

#232 — on a multi-track crossing, one barrier stands between the rails. The ticket already measures three tracks against the register's aantal_sporen: 1, and place_crossings already builds the rail geometry that answers it. Third of the same family; the other two landed yesterday.
#234 — you walk and drive straight through a level crossing. A mast either reaches the collider index or it does not, so the test is a count. Now that #231 has landed and the booms stand up, the remaining defect is walking through a 3.1 m steel post.
#268 — with the height layer on, every floating navigation mark sinks. Two settled captures with one flag between them: 25 pixels of visible buoy without --height, 11 with it. Two measured layers contradicting each other, and the fix is a rule — a floating thing takes the water's level.

I bounded #234 and #268 in their comments because both edit map_geometry.rs, which is the shape of merge that broke main last week.

Filed

#280 — the QA lane has never walked docs/qa/targets.md. The re-verify loop returns before the standing list is reached, and it cannot tell a merged map layer from a merged verdict.
#281 — alreadyFiled fetches one page of issues with limit=100, and this server caps a page at 50. Every duplicate-suppression key silently expires after 50 issues. Proof: #206 was QA'd twice, #210 and #266, both carrying the same key. This is the one I labelled autonomous — it is a one-line fix with a test.
#282 — merging into a red main, with the run-by-run table above.
#283 — the issue agent crashed on .git/config.lock starting #278 and the whole QA pass was lost; the ticket now sits on agent:failed and nothing retries it.

Proposed

#284 — the unattended lane has only ever looked at the map half of the twin. All 34 gaps are about map layers; the simulator, accounts, prims, scripting, chat and voice have had no unattended attention at all. docs/direction.md never says the lane is map-only, but everything in it points that way. I propose it answer the question either way, and if the answer is yes, give the standing list a floor of one pass a week.

For you to decide

Four machinery tickets now sit behind the fence (#280, #282, #283, plus #220, #270, #271 from before), and three finished branches are still unlanded. I deliberately labelled only one of my four autonomous rather than adding three more branches to a pile that is already the bottleneck. #221, #272 and now #284 are three proposals waiting on one answer each.

No commits were made.

_{🤖 viberfox issue agent on the VPS — 57 turns · $6.28 · session b2a1d238-a9ea-4dcd-a228-645197603adc. Reply with @agent to continue this session.}

I read the last seven days, promoted three gaps, filed four machinery tickets and one proposal, and closed #279. No code changed — this ticket asks for steering, not building — so the branch has no commits and was not pushed. ## The period, in five lines - **74 issues in seven days. Twelve of them were about a public dataset; the other sixty-two were the lane looking at its own output.** Three data sources reached the world (crop parcels, navigation marks, level crossings), all on 30 August; nine more candidates were checked and rejected, which is durable work. - **The last retrospective's three promotions all shipped.** #231, #233 and #267 were built, merged and deployed on 2 September. The promotion path works; it is the only thing that has ever closed a `qa-gap` (3 closed, 31 still open). - **Three tickets were merged in 63 minutes on 2 September while `main` was already red, and every one of the three merge commits was red.** The deploy refused each time and said so on each ticket; nothing read that back. - **Every QA pass the lane has ever filed — 14 of 14 — re-verified a recently shipped ticket, nine of them documentation-only verdicts.** The standing list of player-facing functionality in `docs/qa/targets.md` has never been walked once. That is why 11 of the 31 open gaps are "this note points at the wrong file". - **#214 is still finished and unlanded, now four days.** #219 and #237 are still waiting too. ## Promoted (`autonomous` + `ship`, with a reason on each) - **#232 — on a multi-track crossing, one barrier stands between the rails.** The ticket already measures three tracks against the register's `aantal_sporen: 1`, and `place_crossings` already builds the rail geometry that answers it. Third of the same family; the other two landed yesterday. - **#234 — you walk and drive straight through a level crossing.** A mast either reaches the collider index or it does not, so the test is a count. Now that #231 has landed and the booms stand up, the remaining defect is walking through a 3.1 m steel post. - **#268 — with the height layer on, every floating navigation mark sinks.** Two settled captures with one flag between them: 25 pixels of visible buoy without `--height`, 11 with it. Two measured layers contradicting each other, and the fix is a rule — a floating thing takes the water's level. I bounded #234 and #268 in their comments because both edit `map_geometry.rs`, which is the shape of merge that broke `main` last week. ## Filed - **#280** — the QA lane has never walked `docs/qa/targets.md`. The re-verify loop returns before the standing list is reached, and it cannot tell a merged map layer from a merged verdict. - **#281** — `alreadyFiled` fetches one page of issues with `limit=100`, and this server caps a page at 50. Every duplicate-suppression key silently expires after 50 issues. Proof: #206 was QA'd twice, #210 and #266, both carrying the same key. **This is the one I labelled `autonomous`** — it is a one-line fix with a test. - **#282** — merging into a red `main`, with the run-by-run table above. - **#283** — the issue agent crashed on `.git/config.lock` starting #278 and the whole QA pass was lost; the ticket now sits on `agent:failed` and nothing retries it. ## Proposed **#284 — the unattended lane has only ever looked at the map half of the twin.** All 34 gaps are about map layers; the simulator, accounts, prims, scripting, chat and voice have had no unattended attention at all. `docs/direction.md` never says the lane is map-only, but everything in it points that way. I propose it answer the question either way, and if the answer is yes, give the standing list a floor of one pass a week. ## For you to decide **Four machinery tickets now sit behind the fence** (#280, #282, #283, plus #220, #270, #271 from before), and three finished branches are still unlanded. I deliberately labelled only one of my four `autonomous` rather than adding three more branches to a pile that is already the bottleneck. #221, #272 and now #284 are three proposals waiting on one answer each. _No commits were made._ _No commits were made._ --- 🤖 viberfox issue agent on the VPS — 57 turns · $6.28 · session `b2a1d238-a9ea-4dcd-a228-645197603adc`. Reply with **@agent** to continue this session.

viberfox-agent added

agent:done

and removed

agent:running

labels

2026-09-03 01:00:28 +00:00

viberfox-agent referenced this issue

2026-09-04 00:30:53 +00:00

alreadyFiled only ever sees 50 issues, so every autopilot dedupe key silently expires — #206 was QA'd twice #281