paliad

m/paliad

Fork 0

Commit Graph

Author	SHA1	Message	Date
m	438e73fd13	docs(t-paliad-149): renumber migrations 058→060 (PR 1) and 059→061 (PR 2) 058 = paliadin_poc (t-146), 059 = profession_vs_responsibility (t-148), both shipped on main 2026-05-07. Next available is 060. Per maria's coder-shift instruction.	2026-05-07 22:15:22 +02:00
m	b9824dd86f	docs(t-paliad-149): lock 4 surfaced questions per m's AskUserQuestion answers m's locks (2026-05-07 22:08): - Q1 default landing → last-viewed restore (sessionStorage; URL params override; first-visit fallback Tree+Alle+top-level) - New-Q20 cards default content → rich (~9 facts: title+type+status+clientmatter+parent path+deadline counts+next 3+last 3+team) - New-Q21 cards customisation → FULL drag-rearrange + named layouts (new paliad.user_card_layouts table, migration 059) - Q13 search shape → both (in-place page filter on active view + global Cmd-K palette unchanged) Implementation impact: PR 2 grows from ~700-900 LoC to ~1300-1700 LoC because m chose (c) full drag-rearrange over (b) localStorage-only. New backend service CardLayoutService + JSON validator + 5 endpoints; frontend gets edit-mode chrome + HTML5 drag-and-drop + layout dropdown. Optional internal PR 2a / PR 2b split if review feels heavy (read-only cards first, then customisation). PR 1 (tree + chips + pin + search) is unchanged at ~1100-1400 LoC. Other 17 recommendations stay READY-FOR-REVIEW per the dogma.	2026-05-07 22:11:18 +02:00
m	397a9b1854	docs(t-paliad-149): inventor design — projects page redesign (tree-first + chips + pinning + cards) Three view modes (Tree default \| Cards \| Flat), chip filter row, pinning, search-as-tree-filter, mobile drill-in. Cards view (m's addition) has configurable content + per-user prefs in localStorage v1. Q15 decision (delegated to inventor): bespoke /projects, NOT Custom Views. Custom Views is event-shaped; projects are scope, not events. Adding SourceProject + ShapeTree to t-144's substrate would break shape ⊥ source orthogonality. Reversible if a unifying abstraction emerges. Two-PR phasing: PR 1 = tree + chips + pin + search (~1100-1400 LoC, migration 058). PR 2 = Cards view + customisation modal + cards-preview endpoint (~700-900 LoC, additive on PR 1). 4 surfaced questions for m via AskUserQuestion: default landing + view mode, cards default content, cards customisation scope, search shape. Other 17 questions answered with recommendations + rationale per the dogma (make it easy for m). Awaiting m's go on §12 questions before locking. NO coder shift until lock.	2026-05-07 22:05:44 +02:00

Author

SHA1

Message

Date

438e73fd13

docs(t-paliad-149): renumber migrations 058→060 (PR 1) and 059→061 (PR 2)

058 = paliadin_poc (t-146), 059 = profession_vs_responsibility (t-148), both shipped on main 2026-05-07. Next available is 060.

Per maria's coder-shift instruction.

2026-05-07 22:15:22 +02:00

b9824dd86f

docs(t-paliad-149): lock 4 surfaced questions per m's AskUserQuestion answers

m's locks (2026-05-07 22:08):
- Q1 default landing → last-viewed restore (sessionStorage; URL params override; first-visit fallback Tree+Alle+top-level)
- New-Q20 cards default content → rich (~9 facts: title+type+status+clientmatter+parent path+deadline counts+next 3+last 3+team)
- New-Q21 cards customisation → FULL drag-rearrange + named layouts (new paliad.user_card_layouts table, migration 059)
- Q13 search shape → both (in-place page filter on active view + global Cmd-K palette unchanged)

Implementation impact: PR 2 grows from ~700-900 LoC to ~1300-1700 LoC because
m chose (c) full drag-rearrange over (b) localStorage-only. New backend
service CardLayoutService + JSON validator + 5 endpoints; frontend gets
edit-mode chrome + HTML5 drag-and-drop + layout dropdown. Optional internal
PR 2a / PR 2b split if review feels heavy (read-only cards first, then
customisation).

PR 1 (tree + chips + pin + search) is unchanged at ~1100-1400 LoC.
Other 17 recommendations stay READY-FOR-REVIEW per the dogma.

2026-05-07 22:11:18 +02:00

397a9b1854

docs(t-paliad-149): inventor design — projects page redesign (tree-first + chips + pinning + cards)

Three view modes (Tree default | Cards | Flat), chip filter row, pinning,
search-as-tree-filter, mobile drill-in. Cards view (m's addition) has
configurable content + per-user prefs in localStorage v1.

Q15 decision (delegated to inventor): bespoke /projects, NOT Custom Views.
Custom Views is event-shaped; projects are scope, not events. Adding
SourceProject + ShapeTree to t-144's substrate would break shape ⊥ source
orthogonality. Reversible if a unifying abstraction emerges.

Two-PR phasing: PR 1 = tree + chips + pin + search (~1100-1400 LoC,
migration 058). PR 2 = Cards view + customisation modal + cards-preview
endpoint (~700-900 LoC, additive on PR 1).

4 surfaced questions for m via AskUserQuestion: default landing + view mode,
cards default content, cards customisation scope, search shape. Other 17
questions answered with recommendations + rationale per the dogma (make it
easy for m).

Awaiting m's go on §12 questions before locking. NO coder shift until lock.

2026-05-07 22:05:44 +02:00

3 Commits