Motir

Estimate: 30m

The design asset for making board SETTINGS per-board. Today the 3.6 board-config admin only configures the project DEFAULT board: settings/project/board resolves the default board, and every entry point (the column [⋯] “Board settings →”, the unmapped-tray “Map columns”, the settings landing card) links there with NO board context. With many boards per project (3.7) each board has its OWN columns / column→status mapping / swimlane group-by / WIP (all already board-scoped in the schema), so settings must target the SELECTED board — this gap is unspecified in design/boards/, so the design gate produces it FIRST (gates 3.7.8).

Verified mirror (rung 1, mistake #33): in Jira each board has its OWN configuration, reached FROM that board (board → ⋯ → Board settings / Configure board), and the config screen names the board it edits + lets you switch board. Per-board settings reached from the board is the standard; default-only is the gap.

Specify: (a) a “Board settings” item in the switcher manage menu (the 3.7.4 manage menu — alongside Rename / Set as default / Delete) that opens the settings page for THAT board; (b) the settings-page board context — settings/project/board gains a header that NAMES the board being configured + a board switcher to change which board you’re editing (reuse the 3.7.4 switcher vocabulary), since the page is now per-board; (c) the column [⋯] “Board settings →” + unmapped-tray “Map columns” + the settings landing card carry the active board. Output: extend design/boards/ (a *.mock.html from components/ui/* + --el-*/shape tokens) + PNG + a “Per-board settings (Story 3.7)” section in design/boards/design-notes.md.

Acceptance criteria

• The asset + a “Per-board settings (Story 3.7)” notes section exist; built from components/ui/* + --el-*/element-shape tokens (no Tier-0 --color-*, no raw shape utilities), AA-safe, passes the render checklist.
• Draws: the manage-menu “Board settings” item, the settings-page header naming the board + its board switcher, and the per-board scoping of the column [⋯] / unmapped-tray / landing-card entries.
• design-notes.md names the composing primitives (the manage-menu item, the switcher reuse, the settings-page header) and states board settings is membership-gated now / project-admin-gated under Story 6.4.

Context refs

• design/boards/multi-board.mock.html + design-notes.md (3.7.1 — the switcher + manage menu this extends); design/boards/board-config.mock.html (3.6.1 — the settings surface getting board context)
• components/ui/* (the dropdown Menu, the board switcher); Jira’s per-board “Configure board” as the mirror (rung 1)