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

viberfox-agent commented

2026-09-02 06:50:02 +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-02 06:50:02 +00:00

viberfox-agent added this to the Viberfox project

2026-09-02 06:50:07 +00:00

viberfox-agent added the

agent:running

label

2026-09-02 06:50:07 +00:00

viberfox-agent commented

2026-09-02 06:50:11 +00:00

Author

Collaborator

🤖 Picked this up — working on branch feat/269-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/269-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-02 06:54:40 +00:00

gap: every level crossing is drawn with its barriers permanently lowered across the road #231

viberfox-agent referenced this issue

2026-09-02 06:54:40 +00:00

gap: a crossing is sized for a 7 m road, so its booms stop short and its masts stand in the carriageway #233

viberfox-agent referenced this issue

2026-09-02 06:54:40 +00:00

gap: a cell's ground waits on api.pdok.nl before it is tessellated #267

viberfox-agent referenced this issue

2026-09-02 06:55:10 +00:00

The daily digest reports Stuck, waiting for you: none while three tickets wait for a person #270

viberfox-agent referenced this issue

2026-09-02 06:55:36 +00:00

A conflict-parked branch has no way back into the lane — #214 has been finished and unlanded for three days #271

viberfox-agent referenced this issue

2026-09-02 06:56:15 +00:00

proposal: a qa-gap needs a way out — 34 filed, 0 closed, and the only exit is three promotions a retrospective #272

viberfox-agent closed this issue

2026-09-02 06:56:21 +00:00

viberfox-agent commented

2026-09-02 06:56:49 +00:00

Author

Collaborator

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

The period, in five lines

100 issues were created between 26 August and 2 September. 34 of them are qa-gap findings, and none has been closed or started.
The last three days produced no new data source at all: everything went into quality checks of what had already shipped. That is arguably right, but it means the only queue with anything in it is one nothing can drain.
The previous retrospective's three promotions closed zero gaps. #213 stopped asking a question nobody is there to answer; #214 was built, works, and has sat on a merge conflict for three days; the third was never picked up.
Three finished branches are unlanded (#214, #219, #237), and the shipping setting is off. The bottleneck this period was not finding work and not building it — it was everything after "done".
The daily note on 2 September said "Stuck, waiting for you: none" on a day when three tickets were waiting for a person.

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

#231 — level-crossing booms are drawn lying across the road. The module note, the constant's own comment and the notes file all say the booms stand raised; the code builds them horizontal. No decision to make, and the ticket names its own test: the boom's bounding box should be taller than it is wide.
#233 — a crossing is sized for a 7 metre road, so its masts stand on the asphalt. The measured width is already on a lookup the code performs anyway, in the same module, put there so the two could not drift. Judged from vertex positions against the two committed fixtures.
#267 — a cell's ground, roads and buildings wait on api.pdok.nl before anything is drawn. A slow third party reads as no map, not as no buoys. I chose the fix direction in the promotion comment — the two requests concurrent, a short timeout passed at the call site, a failure cached — precisely so this cannot stall the way #213 did.

I left the six gaps that are blocked on the cartopy repository, the eleven that are wrong pointers in documentation, and everything needing a taste judgement.

Filed

#270 — the daily note cannot see a ticket waiting for a person. Three causes, all in digest(): it filters on the autopilot label, so every promoted ticket is invisible; the fence refusal and the conflict park add no label, so the "stuck" bucket misses them; and "being built" is whatever is left over, which is how a proposal got reported as under construction.
#271 — a branch that conflicts with main has no way back. The park tells a person to rebase, and this lane's premise is that there is no person. #214 is the proof. A rebase is worth one attempt before parking; re-merging is not.

Both are in tools/autopilot.ts, so the lane may build them and may not merge them.

Proposed

#272 — a qa-gap needs a way out. docs/direction.md says a lot about what may be built and nothing about what becomes of a finding. Four asks: let a gap be closed as not worth doing; sweep documentation-accuracy findings in one batch instead of eleven tickets; keep gaps that can only be fixed in cartopy out of this queue; and stop the quality lane filing a seventh finding on a layer that already has six open. It is the successor to #221, which is still open and still worth an answer.

For you to decide

Shipping is off and three finished branches are stacked behind it, one of them a working feature from the last retrospective. Nothing I filed changes that.

No commits were made.

_{🤖 viberfox issue agent on the VPS — 29 turns · $3.80 · session 81c89f98-beec-454c-a8d8-8e7bf2c695f8. Reply with @agent to continue this session.}

I read the seven days, promoted three gaps, filed two machinery tickets and one proposal, and closed #269. No code was changed — this ticket asks for steering, not building — so the branch has no commits and was not pushed. ## The period, in five lines - **100 issues were created between 26 August and 2 September.** 34 of them are `qa-gap` findings, and **none has been closed or started.** - The last three days produced **no new data source at all**: everything went into quality checks of what had already shipped. That is arguably right, but it means the only queue with anything in it is one nothing can drain. - **The previous retrospective's three promotions closed zero gaps.** #213 stopped asking a question nobody is there to answer; #214 was built, works, and has sat on a merge conflict for three days; the third was never picked up. - **Three finished branches are unlanded** (#214, #219, #237), and the shipping setting is off. The bottleneck this period was not finding work and not building it — it was everything after "done". - The daily note on 2 September said **"Stuck, waiting for you: none"** on a day when three tickets were waiting for a person. ## Promoted (added `autonomous` + `ship`, with a reason on each) - **#231 — level-crossing booms are drawn lying across the road.** The module note, the constant's own comment and the notes file all say the booms stand raised; the code builds them horizontal. No decision to make, and the ticket names its own test: the boom's bounding box should be taller than it is wide. - **#233 — a crossing is sized for a 7 metre road, so its masts stand on the asphalt.** The measured width is already on a lookup the code performs anyway, in the same module, put there so the two could not drift. Judged from vertex positions against the two committed fixtures. - **#267 — a cell's ground, roads and buildings wait on `api.pdok.nl` before anything is drawn.** A slow third party reads as no map, not as no buoys. **I chose the fix direction in the promotion comment** — the two requests concurrent, a short timeout passed at the call site, a failure cached — precisely so this cannot stall the way #213 did. I left the six gaps that are blocked on the cartopy repository, the eleven that are wrong pointers in documentation, and everything needing a taste judgement. ## Filed - **#270** — the daily note cannot see a ticket waiting for a person. Three causes, all in `digest()`: it filters on the `autopilot` label, so every promoted ticket is invisible; the fence refusal and the conflict park add no label, so the "stuck" bucket misses them; and "being built" is whatever is left over, which is how a proposal got reported as under construction. - **#271** — a branch that conflicts with `main` has no way back. The park tells a person to rebase, and this lane's premise is that there is no person. #214 is the proof. A rebase is worth one attempt before parking; re-merging is not. Both are in `tools/autopilot.ts`, so the lane may build them and may not merge them. ## Proposed **#272 — a `qa-gap` needs a way out.** `docs/direction.md` says a lot about what may be built and nothing about what becomes of a finding. Four asks: let a gap be closed as not worth doing; sweep documentation-accuracy findings in one batch instead of eleven tickets; keep gaps that can only be fixed in cartopy out of this queue; and stop the quality lane filing a seventh finding on a layer that already has six open. It is the successor to #221, which is still open and still worth an answer. ## For you to decide Shipping is off and three finished branches are stacked behind it, one of them a working feature from the last retrospective. Nothing I filed changes that. _No commits were made._ --- 🤖 viberfox issue agent on the VPS — 29 turns · $3.80 · session `81c89f98-beec-454c-a8d8-8e7bf2c695f8`. Reply with **@agent** to continue this session.

viberfox-agent added

agent:done

and removed

agent:running

labels

2026-09-02 06:56:49 +00:00

viberfox-agent referenced this issue

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

Autopilot log #257

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