|
| 1 | +# BUILD_PR_LEVEL_21_4_TOOL_ALIGNMENT_AND_HEADER_REAL_ESTATE |
| 2 | + |
| 3 | +## Purpose |
| 4 | +Execute the next combined safe tools lane by using the 21.3 tool-quality baseline to drive two adjacent, compatible work streams in one PR: |
| 5 | + |
| 6 | +- reduce real estate used by headers |
| 7 | +- align functionality across tools where applicable |
| 8 | + |
| 9 | +This PR should convert the cross-tool gaps and shared UI inconsistencies found in the baseline into a concrete, validated alignment pass. |
| 10 | + |
| 11 | +## Combined roadmap intent |
| 12 | +This PR may advance the following items only if fully executed and validated: |
| 13 | + |
| 14 | +### UI / UX Improvements |
| 15 | +- `reduce screen real estate used by headers` `[ ] -> [x]` |
| 16 | + |
| 17 | +### Missing Functionality |
| 18 | +- `align functionality across tools where applicable` `[ ] -> [x]` |
| 19 | + |
| 20 | +### Optional additional advancement |
| 21 | +If this PR also fully completes all remaining UI/UX items through real execution and validation, it may additionally advance: |
| 22 | +- `normalize tool layout and spacing` `[ ] -> [x]` |
| 23 | +- `improve panel resizing and docking behavior` `[ ] -> [x]` |
| 24 | +- `ensure consistent control placement across tools` `[ ] -> [x]` |
| 25 | + |
| 26 | +Do **not** update those optional items unless they are truly completed and validated in this same PR. |
| 27 | + |
| 28 | +## Scope |
| 29 | +Included: |
| 30 | +- use the 21.3 bug/gap baseline as the source of truth for shared tool inconsistencies |
| 31 | +- reduce header height, spacing, and vertical waste across primary tools where feasible |
| 32 | +- standardize shared header behavior/patterns across tools |
| 33 | +- align common tool capabilities where those capabilities should behave consistently |
| 34 | +- normalize obvious shared control placement differences where tied directly to the header/alignment pass |
| 35 | +- produce before/after validation evidence |
| 36 | +- preserve unrelated working-tree changes |
| 37 | + |
| 38 | +Excluded: |
| 39 | +- no speculative new tools |
| 40 | +- no unrelated feature expansion |
| 41 | +- no broad design rewrite beyond the aligned header/capability pass |
| 42 | +- no roadmap rewrites |
| 43 | +- no `start_of_day` changes |
| 44 | + |
| 45 | +## Baseline inputs |
| 46 | +Use: |
| 47 | +- tool UAT inventory from 21.2 |
| 48 | +- automation / bugs / missing functionality outputs from 21.3 |
| 49 | + |
| 50 | +If the 21.3 baseline identifies a subset of tools as highest-value for alignment, prioritize those first and record the prioritization rationale. |
| 51 | + |
| 52 | +## Primary tool set |
| 53 | +At minimum evaluate: |
| 54 | +- Asset Browser |
| 55 | +- Palette Browser |
| 56 | +- Parallax Scene Studio |
| 57 | +- Sprite Editor |
| 58 | +- Tilemap Studio |
| 59 | +- Vector Asset Studio |
| 60 | +- Vector Map Editor |
| 61 | +- Tool Host |
| 62 | + |
| 63 | +Also include additional tools where the shared header/layout system applies cleanly. |
| 64 | + |
| 65 | +## Required outputs |
| 66 | +Codex must create/update: |
| 67 | + |
| 68 | +- `docs/dev/reports/BUILD_PR_LEVEL_21_4_TOOL_ALIGNMENT_AND_HEADER_REAL_ESTATE_HEADER_REAL_ESTATE_AUDIT.md` |
| 69 | +- `docs/dev/reports/BUILD_PR_LEVEL_21_4_TOOL_ALIGNMENT_AND_HEADER_REAL_ESTATE_TOOL_ALIGNMENT_MATRIX.md` |
| 70 | +- `docs/dev/reports/BUILD_PR_LEVEL_21_4_TOOL_ALIGNMENT_AND_HEADER_REAL_ESTATE_VALIDATION.md` |
| 71 | + |
| 72 | +If useful for validation evidence: |
| 73 | +- before/after screenshots or report references |
| 74 | +- shared pattern notes describing the normalized header/control model |
| 75 | + |
| 76 | +## Header real-estate requirements |
| 77 | +For each in-scope tool: |
| 78 | +- record current header structure |
| 79 | +- reduce unnecessary vertical usage where possible |
| 80 | +- preserve usability and discoverability |
| 81 | +- avoid hiding critical controls unless replaced with a clearly better compact pattern |
| 82 | + |
| 83 | +Examples of valid changes: |
| 84 | +- compact header rows |
| 85 | +- accordion/collapsible secondary sections |
| 86 | +- reduced padding/margins |
| 87 | +- merged redundant labels/containers |
| 88 | +- shared toolbar patterns |
| 89 | + |
| 90 | +## Alignment requirements |
| 91 | +For each aligned cross-tool capability, document: |
| 92 | +- capability name |
| 93 | +- tools affected |
| 94 | +- previous inconsistency |
| 95 | +- new aligned behavior |
| 96 | +- validation proof |
| 97 | + |
| 98 | +Examples of likely alignment candidates: |
| 99 | +- load/open controls |
| 100 | +- save/export controls |
| 101 | +- project/sample picker placement |
| 102 | +- preview/run controls |
| 103 | +- header action grouping |
| 104 | +- compact toolbar behavior |
| 105 | + |
| 106 | +## Acceptance |
| 107 | +- header real estate is reduced for in-scope tools |
| 108 | +- aligned cross-tool behaviors are documented and validated |
| 109 | +- before/after differences are explicit |
| 110 | +- no unrelated regressions introduced |
| 111 | +- unrelated working-tree changes are preserved |
| 112 | +- roadmap updates are status-only and execution-backed |
| 113 | + |
| 114 | +## Validation requirements |
| 115 | +Validation must confirm: |
| 116 | +- header audit completed |
| 117 | +- alignment matrix completed |
| 118 | +- in-scope tools updated and validated |
| 119 | +- no `start_of_day` changes |
| 120 | +- unrelated working-tree changes preserved |
| 121 | +- roadmap edits limited to items fully completed here |
| 122 | + |
| 123 | +## Roadmap update rules |
| 124 | +Only update status markers in: |
| 125 | +- `docs/dev/roadmaps/MASTER_ROADMAP_TOOLS.md` |
| 126 | + |
| 127 | +Allowed transitions only if fully executed and validated: |
| 128 | +- `reduce screen real estate used by headers` `[ ] -> [x]` |
| 129 | +- `align functionality across tools where applicable` `[ ] -> [x]` |
| 130 | + |
| 131 | +Optional additional transitions only if fully completed and validated in this PR: |
| 132 | +- `normalize tool layout and spacing` `[ ] -> [x]` |
| 133 | +- `improve panel resizing and docking behavior` `[ ] -> [x]` |
| 134 | +- `ensure consistent control placement across tools` `[ ] -> [x]` |
0 commit comments