Define layout tier constraint sets (basic, partial, full, wide) #124

New issue

Open

opened 2026-03-15 04:13:25 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 04:13:25 +00:00

Owner

Metadata

Commit Message: feat(ui): define layout tier constraint sets
Branch: feature/m2-window-layout

Background and Context

Define the window assignments and arrangements for each tier: basic (main+input), partial (main+input+status), full (main+input+status+quickbar+map), wide (all including sidebar).

Acceptance Criteria

Implementation matches specification
BDD test coverage

Subtasks

Implement as specified
Write Cucumber feature file and step definitions

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the
Commit Message in Metadata exactly.
The commit is pushed to the remote on the branch matching the Branch in Metadata.
The commit is submitted as a pull request to master, reviewed, and merged.

## Metadata - **Commit Message**: `feat(ui): define layout tier constraint sets` - **Branch**: `feature/m2-window-layout` ## Background and Context Define the window assignments and arrangements for each tier: basic (main+input), partial (main+input+status), full (main+input+status+quickbar+map), wide (all including sidebar). ## Acceptance Criteria - Implementation matches specification - BDD test coverage ## Subtasks - [ ] Implement as specified - [ ] Write Cucumber feature file and step definitions ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged**.