Skip to content

fix(progress-report): fold the full plan tables under the phase cards - #457

Merged
MendixMau merged 2 commits into
release/v1.0from
fix/progress-report-collapse-plan-tables
Oct 17, 2026
Merged

MendixMau merged 2 commits into
release/v1.0from
fix/progress-report-collapse-plan-tables

Conversation

@MendixMau

Copy link
Copy Markdown
Owner

What went wrong

A user opened the progress report on a live five-app lab project (178 plan rows, 77% built) and said: "the buildplan got merge in. But it's look like horrible HTML, and it takes tooo much room in this progress report no?"

They were right. The build section rendered the phase cards (one compact card per phase, with a bar, counts and a click-to-show row list), and below them the whole build-plan.md fragment again, fully open: every table of every phase, with the claims and drift columns, plus views A and B.

Measure Before After
Page size 229k characters 252k (the token panels came back too, see below)
Share of the page taken by the open plan tables 146k, 64% folded, one summary line
Rows shown twice all 178 none until the reader asks

The phase cards already answer "where are we" for each phase. The open tables underneath pushed the footer and the "how it is measured" notes about 140k characters further down, and the user stopped reading at the first long table.

What went well

  • The phase cards themselves are good: on the same project, the 14 phases fit on one screen with bars, row counts and a "building now" tag on the active phase. Nothing about them changes.
  • The page's own openTarget() script already opens a targeted <details>, so the "Jump to the plan tables" link keeps working without new JavaScript.
  • The autoreload already remembers which <details> were open, so a reader who opens the tables keeps them open across the 30-second refresh.

The change

project-bin/progress-report.py: the fragment is wrapped in <details id=plan-tables class='card frag'>, closed by default, with a one-line summary ("Full plan tables and views A and B"). When there is no fragment, nothing is written (before, an empty <div> was).

Why fold and not drop

The tables still carry what the cards do not: the claims and drift per row and the script-folder and module-proof views (A and B). Those are reference material for when a count looks wrong, not the first thing to read.

Tests

  • New P6 in tests/wave2/test-progress-report-polish.sh: the tables are a closed <details> with a summary, the jump link still points at them, the old open <div> is gone.
  • Run locally, all green: test-progress-report-polish 36/0, test-progress-report 101/0, test-progress-report-field-fixes 101/0, test-progress-report-gitignore 15/0, test-surface-column 13/0, test-build-plan-json 70/0.
  • Looked at the rendered build section on the lab project after the change: the 14 phase cards and one folded line, on one screen.

Related

The same session found a second, larger report bug: a stale blueprint.html after a change round reopened Stage 3 and made the report show Stages 3 and 4 at 0% on a project that is 77% built. That one needs a design decision, so it is filed as an issue, not folded into this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WHnXeE4frSGHL5PHSpTJb4

MendixMau and others added 2 commits October 17, 2026 13:43
The build section embedded the whole build-plan.md fragment open below the
phase cards, which already list every row. On a 178-row plan that was 146k of
the page's 229k characters, the same rows twice. The fragment now sits in a
closed <details>; the "Jump to the plan tables" link still opens it.

Test P6 in test-progress-report-polish.sh pins the folded state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WHnXeE4frSGHL5PHSpTJb4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MendixMau
MendixMau merged commit f266192 into release/v1.0 Oct 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant