You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
intake: hold 50 in the Recent feed, show 10, reveal the rest on tap
The table is a glance, not a log. Twenty rows already pushed the Epics below a
scroll on a phone, and capping the feed at what fits on screen is the wrong
trade: a quiet fortnight and a busy week want different depths.
So the feed now holds 50 (RECENT_MAX) and shows 10 (RECENT_PAGE), with the rest
one tap away — and each surface reveals it with what it actually renders:
- Pages twin: every row ships in the DOM, the overflow marked `hidden`, and a
`…` button flips ten at a time before retiring itself. Hidden rather than
absent, so a reader with JS off gets the whole feed instead of ten rows and a
dead button.
- Markdown page: GitHub strips that script, so the reveal is `<details>` —
NESTED, so each tap shows the next ten and leaves another `…` behind it.
Sibling blocks would let a reader open page 4 without page 3, which is not
what "show me more" means on a list ordered by date. Each page carries its
own header row, since a markdown table cannot span an HTML block boundary.
Also fixes the blurb printing literal backticks on the Pages page — it is
shared with the markdown renderer and was never run through `_summary_label`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L4HPWjv5rdzBAkKpfW1SbR
|**reconcile**|`intake reconcile [prefix]`| rank backlog prompts that look already-shipped (vs the `complete/` records / `active/`); always read-only — retiring stays human |
89
89
|**reconcile --repo**|`intake reconcile --repo <target> [prefix]`|**also** read the target repo's source for identifiers the prompts name — the one signal that sees a prompt with no Mind-side trace. Opt-in; the default path is offline |
90
90
91
-
**Recent** is the one section laid out by *date* rather than by state: the 20
91
+
**Recent** is the one section laid out by *date* rather than by state: the 50
92
92
newest events on the **work in hand** — issued, parked, filed — merged across
93
-
the live buckets and sitting between the Backlog and the Epics. Every other
93
+
the live buckets and sitting between the Backlog and the Epics. It *holds* 50
94
+
and *shows* 10 (`RECENT_MAX` / `RECENT_PAGE`): the table is a glance, not a
95
+
log, so the rest is one tap away — a `…` button on the Pages twin, and nested
96
+
`<details>` on the markdown page, which GitHub renders where it strips the
97
+
script. Every other
94
98
section answers "what should I do now?"; recency is orthogonal to state, so
95
99
none of them can answer "what has been happening?". Dates come from the
96
100
registry key that names the event (`issued:` / `parked:` / `filed:`, PyAutoMind
0 commit comments