Document the six-screen maximum and seven main-window layouts #71

Activity

1. pullfrog commented on Sep 26, 2026

   

   pullfrogBot

   on Sep 26, 2026 – with Pullfrog

   More actions

     ^{｜ Build this ➔ ｜ Make a plan ➔}
2. cchacs

   self-assigned this

   on Sep 26, 2026
3. cchacs

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Sep 26, 2026
4. cchacs

   added the

   Task

   issue type on Sep 26, 2026
5. cchacs commented on Oct 1, 2026

   

   cchacs

   on Oct 1, 2026 – with Claude

   CollaboratorAuthor

   More actions

   @pullfrog please build this (Effort: Low). Correct the documentation as laid out in the issue: lead the README with 2–6 synchronized panels and the seven main-window layouts, fix the "2–4 instances" integration wording and .specify/memory/constitution.md, and state explicitly that pop-out windows offer a narrower layout set than the main window. Follow the repo's CLAUDE.md (README links point at got-feedBack, not this fork) and open a PR against main. Please don't merge it.

   ---

   Generated by Claude Code

   👀React with 👀1Reacted by pullfrog
6. pullfrog commented on Oct 1, 2026

   

   pullfrogBot

   on Oct 1, 2026 – with Pullfrog

   Last edited by pullfrog

   More actions

   Opened PR #76 against main (left open, not merged): #76

   Documentation corrected

   • README leads with 2–6 synchronized panels and lists all seven main-window layouts (Five as 2-over-3, Six as 3×2).
   • Pop-out section now states explicitly that a pop-out window's layout set is narrower than the main window's — Single/Top-Bottom/Left-Right/Quad, stopping at Quad — replacing the "same layouts as main" claim that contradicted the list right after it.
   • Path 2 integration rule and the constitution preamble: 2–4 → 2–6 instances.

   Also fixed, because the same claim was stale where users read it first: the plugin.json blurb ("2–4 synced panels"), the tour.json layout-picker step, and the screen.js module header. The Settings default-layout picker also stopped at Quad, so a saved five/six default couldn't be represented — both options added (patch bump to 1.14.22, which the repo's version-bump compliance gate requires for .js/.html changes).

   Drift guard — five tests derive the advertised surface from LAYOUTS/FOLLOWER_LAYOUT_PANELS: the README's range and layout count, the settings options, both picker option lists, and the pop-out set being a strict subset. Each was mutation-checked rather than just run green: renaming the follower map, adding a dead pop-out picker option, and adding a seven layout without doc updates each fail loudly. The first of those initially passed vacuously, so the parsers now assert a non-empty match.

   node --check screen.js clean; node tests/screen.test.js 187 pass, 0 fail. Left out of scope and noted in the PR body: the constitution's Principles IV/VI/VIII still describe the retired createJumpingTabPane/createTabView factories, its Governance section names the old topkoa repo, and CLAUDE.md:30/:46 under-describe LAYOUTS and the layout values.

   Task list (8/8 completed)

   • Create feature branch
   • Read the issue text thoroughly
   • Update README.md with 2–6 screens, seven main-window layouts, corrected integration wording, popup layout clarification
   • Update constitution.md from 2–4 to 2–6
   • Update settings.html default-layout dropdown to list all seven layouts
   • Add test pinning README's advertised max/layout count to LAYOUTS so it can't drift again
   • Run tests
   • Self-review diff, commit, push, open PR (do not merge)

     ^{｜ View workflow run ｜ via Pullfrog ｜ Using big-pickle (free) ｜ 𝕏}
7. cchacs

   closed this as completedon Oct 2, 2026