file #46-#53
Message
file #46-#53
Diff
.forge/issues/16580f39-0650-47a3-b9e2-01aa7390b402/issue.md+13 −0
--- /dev/null+++ b/.forge/issues/16580f39-0650-47a3-b9e2-01aa7390b402/issue.md@@ -0,0 +1,13 @@1+---2+id: 16580f39-0650-47a3-b9e2-01aa7390b4023+title: Right-align footer text4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:27.020580294Z10+updated: null11+---12+Context: Owner QA — footer text should sit right.13+Tasks: footer line `text-align:right` (all pages, both themes). Tests: CSS assert. Same branch `m6/finish2`.
.forge/issues/2e224780-75f5-456f-9391-4b9c92ae214f/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/2e224780-75f5-456f-9391-4b9c92ae214f/issue.md@@ -0,0 +1,17 @@1+---2+id: 2e224780-75f5-456f-9391-4b9c92ae214f3+title: 'Cards: title first, number second'4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:11.441499273Z10+updated: null11+---12+Context: Owner QA — mobile cards read "12 · some title"; should read "some title · 12".13+Tasks:14+1. Card cell order: title/message FIRST, then number/sha/meta line. Implement via cell order in templates (not CSS order hacks — DOM order = reading order). Desktop table column order UNCHANGED (number first is fine there).15+2. Applies to issues, pulls, commits, tasks, ci, releases cards.16+3. Tests: card HTML asserts title precedes number/sha in DOM.17+Swarm: same agent as #46. Branch `m6/cards2`. Close both.
.forge/issues/56572b62-9b92-4636-8ec4-3fe9ab477b16/issue.md+14 −0
--- /dev/null+++ b/.forge/issues/56572b62-9b92-4636-8ec4-3fe9ab477b16/issue.md@@ -0,0 +1,14 @@1+---2+id: 56572b62-9b92-4636-8ec4-3fe9ab477b163+title: 2x header logo size4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:27.017596122Z10+updated: null11+---12+Context: Owner QA — header logo too small. Double it.13+Tasks: .site-logo 24px -> 48px rendered (keep svg vector; header bar grows accordingly; nav stays vertically centered). Mobile: same (bar wraps if needed, no overlap).14+Tests: size asserts. Same branch `m6/finish2`.
.forge/issues/78c8e17f-f558-4544-b88d-d29ba5a76e65/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/78c8e17f-f558-4544-b88d-d29ba5a76e65/issue.md@@ -0,0 +1,17 @@1+---2+id: 78c8e17f-f558-4544-b88d-d29ba5a76e653+title: Open issues first in table4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:11.444576394Z10+updated: null11+---12+Context: Owner QA — open issues should top the issues table.13+Tasks:14+1. Issues index sort: open first (reverse-chron within), then closed (reverse-chron within). Same for pulls (open incl drafts first, then closed/merged). Display numbers unchanged (still creation rank).15+2. Add small group labels? NO — keep one table, open block then closed block (a hairline divider row is fine, keep tiny).16+3. Tests: fixture mixed states asserts row order + numbers stable.17+Swarm: pair with #49 (same sort code). Branch `m6/sort`.
.forge/issues/99db5711-d98e-4098-bf26-448874da8280/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/99db5711-d98e-4098-bf26-448874da8280/issue.md@@ -0,0 +1,17 @@1+---2+id: 99db5711-d98e-4098-bf26-448874da82803+title: Issues/pulls newest-first4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:11.450209380Z10+updated: null11+---12+Context: Owner QA — issues and pulls should read newest-first.13+Tasks:14+1. Within each state group (#48): reverse chronological (created desc, id desc tiebreak). Numbers stay creation-rank (may appear unordered — correct, note in test).15+2. Same for pulls (and keep commits newest-first as today — verify, no change).16+3. Tests: fixture asserts exact row order by created desc.17+Swarm: same agent as #48. Branch `m6/sort`. Close both.
.forge/issues/d9c80bee-2789-44b9-8569-bd4aba73fd83/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/d9c80bee-2789-44b9-8569-bd4aba73fd83/issue.md@@ -0,0 +1,17 @@1+---2+id: d9c80bee-2789-44b9-8569-bd4aba73fd833+title: Consistent page-head spacing everywhere4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:27.012974159Z10+updated: null11+---12+Context: Owner QA — vertical rhythm differs between code tab, +button pages, plain pages.13+Tasks:14+1. Unify: one page-head pattern (h1 row) + one content-start margin everywhere. Audit code/issues/pulls/commits/tasks/ci/releases/wiki/agents/forms: same nav->head gap, same head->content gap (single CSS vars, e.g. --gap-head, --gap-content). Mobile gaps slightly tighter via existing breakpoint.15+2. Tests: gap-var asserts, per-page head structure asserts.16+Swarm: pair with #51+#52+#53 (layout/CSS area, one agent, one branch).17+Branch `m6/finish2`.
.forge/issues/dcc037bc-8e60-4fc2-b10f-eba2c97c1db7/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/dcc037bc-8e60-4fc2-b10f-eba2c97c1db7/issue.md@@ -0,0 +1,17 @@1+---2+id: dcc037bc-8e60-4fc2-b10f-eba2c97c1db73+title: File table stays a table on mobile4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:11.438209473Z10+updated: null11+---12+Context: Owner QA — file table on code page must stay a real table on all widths (it's dense reference data, not a feed).13+Tasks:14+1. Exempt `.file-table` from the stacked-card reflow: table layout at every width, inside the existing horizontal scroll container if needed on 360px. All OTHER list tables keep cards.15+2. Keep truncation + message/age columns (they make the table fit); file table may scroll horizontally on phones — explicitly accepted here, owner prefers it.16+3. Tests: file-table has no data-label card treatment; scroll wrapper present.17+Swarm: pair with #47 (same card code). Branch `m6/cards2`.
.forge/issues/e705e34d-a03e-48c9-a246-4d607ed95e77/issue.md+17 −0
--- /dev/null+++ b/.forge/issues/e705e34d-a03e-48c9-a246-4d607ed95e77/issue.md@@ -0,0 +1,17 @@1+---2+id: e705e34d-a03e-48c9-a246-4d607ed95e773+title: Branch+CI into clone summary, drop dupe line4+state: open5+labels:6+- area:render7+assignees: []8+milestone: m6-polish9+created: 2026-09-10T08:48:27.023552866Z10+updated: null11+---12+Context: Owner QA — "Branch master @ sha / CI: pass" duplicates the clone summary line. Move branch+sha+CI INTO the Clone & download box (visible in collapsed summary: "Clone & download · master @ sha · CI pass"), delete the standalone repo-meta line.13+Tasks:14+1. Summary shows: Clone & download · <branch> @ <short> · CI <badge>. Full meta (clone cmds, bundle/tarball, sizes) stays inside details.15+2. Remove old repo-meta branch/CI line (keep description + counts? description stays on code head; counts already removed).16+3. Tests: summary asserts, no-duplication assert (branch name appears once outside details content... define: appears in summary, not in a separate meta line).17+Swarm: same branch `m6/finish2` (code template area overlaps #50 agent — SAME agent does all four).