coilyco-gaming/eco-app

Watch

User surfaces: actionable dossier + fix day-as-float / add hour + remove the all-users listing (closes #86) #93

New issue

Closed

opened 2026-07-07 06:11:11 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-07 06:11:11 +00:00

Owner

Remove the all-users listing (`/users`)

Drop the /users route and frontend/src/pages/Users.tsx (plus Users.test.tsx). Keep the per-user dossier /users/:hex (User.tsx) untouched as a surface.
Remove the backend index that fed it: preview_users_json route in src/eco_mcp_app/http_app.py and the users-index path in src/eco_mcp_app/users.py (keep the single-user dossier fetch).
Fix the now-dead inbound links in User.tsx ("All users ->", "Browse every user ->") so nothing points at the removed page.

Fix "day as a float" and add the hour (`frontend/src/pages/User.tsx`)

The dossier renders raw floats: trades table {t.day ?? "-"}, civics Day {e.day}, timeline {ev.day}. These show ugly floats. Every place that mentions a day must also mention the hour, formatted from the underlying timestamp, never a bare float. Use the shared day+hour / relative-time formatter (authored in the site-wide polish ticket) if present, else format inline and leave a note so the sweep can converge them.

Make the dossier actionable for that specific player

Kai: "the per user page should orient around providing actionable info for that specific user - the existing info is fine too though." Keep every existing panel, but lead with an actionable summary that answers what this player would want at a glance:

What are they selling right now and what are they buying (their open offers / orders from the market spine).
What they are best positioned to make and sell (their high-level specialties crossed with current supply gaps / demand).
Recent activity in relative time (hours / days ago), not bare day floats.

Pull supply/demand/offers from the same spine /trade and the item pages use (logistics.py, stores.py, market.py).

Done when

/users is gone with no dead links, the dossier leads with an actionable per-player summary while retaining the existing panels, and every day shows an hour with no raw floats. ward exec test + lint gates green. Update docs/FEATURES.md.

Reshape the user surfaces around actionable per-player info, fix the day rendering, and remove the all-users listing page. Filed from a batch of eco-app feedback Kai handed the director surface. Closes #86 (remove the page that lists every user). ## Remove the all-users listing (`/users`) - Drop the `/users` route and `frontend/src/pages/Users.tsx` (plus `Users.test.tsx`). Keep the per-user dossier `/users/:hex` (`User.tsx`) untouched as a surface. - Remove the backend index that fed it: `preview_users_json` route in `src/eco_mcp_app/http_app.py` and the users-index path in `src/eco_mcp_app/users.py` (keep the single-user dossier fetch). - Fix the now-dead inbound links in `User.tsx` ("All users ->", "Browse every user ->") so nothing points at the removed page. ## Fix "day as a float" and add the hour (`frontend/src/pages/User.tsx`) - The dossier renders raw floats: trades table `{t.day ?? "-"}`, civics `Day {e.day}`, timeline `{ev.day}`. These show ugly floats. Every place that mentions a day must also mention the hour, formatted from the underlying timestamp, never a bare float. Use the shared day+hour / relative-time formatter (authored in the site-wide polish ticket) if present, else format inline and leave a note so the sweep can converge them. ## Make the dossier actionable for that specific player Kai: "the per user page should orient around providing actionable info for that specific user - the existing info is fine too though." Keep every existing panel, but lead with an actionable summary that answers what this player would want at a glance: - What are they selling right now and what are they buying (their open offers / orders from the market spine). - What they are best positioned to make and sell (their high-level specialties crossed with current supply gaps / demand). - Recent activity in relative time (hours / days ago), not bare day floats. Pull supply/demand/offers from the same spine `/trade` and the item pages use (`logistics.py`, `stores.py`, `market.py`). ## Done when `/users` is gone with no dead links, the dossier leads with an actionable per-player summary while retaining the existing panels, and every day shows an hour with no raw floats. `ward exec` test + lint gates green. Update `docs/FEATURES.md`.

coilysiren added the

labels

2026-07-07 06:12:47 +00:00

coilyco-ops commented

2026-07-07 06:13:33 +00:00

Owner

🔒 Reserved by ward agent --driver claude — container engineer-claude-eco-app-93 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-07T06:13:28Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-gaming/eco-app#93 · branch issue-93 · driver claude · workflow direct-main
Run: engineer-claude-eco-app-93 · ward v0.419.0 · dispatched 2026-07-07T06:13:28Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Issue body as seeded:

Reshape the user surfaces around actionable per-player info, fix the day rendering, and remove the all-users listing page. Filed from a batch of eco-app feedback Kai handed the director surface. Closes #86 (remove the page that lists every user).

## Remove the all-users listing (`/users`)

- Drop the `/users` route and `frontend/src/pages/Users.tsx` (plus `Users.test.tsx`). Keep the per-user dossier `/users/:hex` (`User.tsx`) untouched as a surface.
- Remove the backend index that fed it: `preview_users_json` route in `src/eco_mcp_app/http_app.py` and the users-index path in `src/eco_mcp_app/users.py` (keep the single-user dossier fetch).
- Fix the now-dead inbound links in `User.tsx` ("All users -&gt;", "Browse every user -&gt;") so nothing points at the removed page.

## Fix "day as a float" and add the hour (`frontend/src/pages/User.tsx`)

- The dossier renders raw floats: trades table `{t.day ?? "-"}`, civics `Day {e.day}`, timeline `{ev.day}`. These show ugly floats. Every place that mentions a day must also mention the hour, formatted from the underlying timestamp, never a bare float. Use the shared day+hour / relative-time formatter (authored in the site-wide polish ticket) if present, else format inline and leave a note so the sweep can converge them.

## Make the dossier actionable for that specific player

Kai: "the per user page should orient around providing actionable info for that specific user - the existing info is fine too though." Keep every existing panel, but lead with an actionable summary that answers what this player would want at a glance:

- What are they selling right now and what are they buying (their open offers / orders from the market spine).
- What they are best positioned to make and sell (their high-level specialties crossed with current supply gaps / demand).
- Recent activity in relative time (hours / days ago), not bare day floats.

Pull supply/demand/offers from the same spine `/trade` and the item pages use (`logistics.py`, `s

… (truncated to 2000 chars; full body is on this issue)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.419.0).

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-eco-app-93` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-07T06:13:28Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-gaming/eco-app#93` · branch `issue-93` · driver `claude` · workflow `direct-main` - **Run:** `engineer-claude-eco-app-93` · ward `v0.419.0` · dispatched `2026-07-07T06:13:28Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). **Issue body as seeded:** ``` Reshape the user surfaces around actionable per-player info, fix the day rendering, and remove the all-users listing page. Filed from a batch of eco-app feedback Kai handed the director surface. Closes #86 (remove the page that lists every user). ## Remove the all-users listing (`/users`) - Drop the `/users` route and `frontend/src/pages/Users.tsx` (plus `Users.test.tsx`). Keep the per-user dossier `/users/:hex` (`User.tsx`) untouched as a surface. - Remove the backend index that fed it: `preview_users_json` route in `src/eco_mcp_app/http_app.py` and the users-index path in `src/eco_mcp_app/users.py` (keep the single-user dossier fetch). - Fix the now-dead inbound links in `User.tsx` ("All users ->", "Browse every user ->") so nothing points at the removed page. ## Fix "day as a float" and add the hour (`frontend/src/pages/User.tsx`) - The dossier renders raw floats: trades table `{t.day ?? "-"}`, civics `Day {e.day}`, timeline `{ev.day}`. These show ugly floats. Every place that mentions a day must also mention the hour, formatted from the underlying timestamp, never a bare float. Use the shared day+hour / relative-time formatter (authored in the site-wide polish ticket) if present, else format inline and leave a note so the sweep can converge them. ## Make the dossier actionable for that specific player Kai: "the per user page should orient around providing actionable info for that specific user - the existing info is fine too though." Keep every existing panel, but lead with an actionable summary that answers what this player would want at a glance: - What are they selling right now and what are they buying (their open offers / orders from the market spine). - What they are best positioned to make and sell (their high-level specialties crossed with current supply gaps / demand). - Recent activity in relative time (hours / days ago), not bare day floats. Pull supply/demand/offers from the same spine `/trade` and the item pages use (`logistics.py`, `s ``` … (truncated to 2000 chars; full body is on this issue) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.419.0). </details>  — Claude (she/her), via `ward agent`

coilysiren referenced this issue

2026-07-07 06:22:25 +00:00

Remove the page that lists every user #86

coilysiren referenced this issue from a commit

2026-07-07 06:30:37 +00:00

feat(ui): actionable user dossier, day+hour clock, drop all-users listing (#93)

coilysiren closed this issue

2026-07-07 06:35:59 +00:00

coilysiren commented

2026-07-07 06:37:11 +00:00

Author

Owner

WARD-OUTCOME: done - /users listing removed, dossier leads with an actionable summary, all day floats now render Day D, HH:MM; test+lint+build+precommit green, landed on main.

Mostly smooth, with one genuine surprise at the very end. The removals and the day+hour fix were clean, and wiring the actionable "At a glance" panel from the same logistics/stores spine /trade uses fell out naturally — owner-matched live offers, top specialties × current supply gaps, and recent trades in relative time, all best-effort so a missing exporter just thins the summary instead of sinking the page.

The fight was the merge. A parallel run had already landed a shared formatDayHour on main — the "site-wide polish ticket" formatter the issue pointed at — but it's the /info world clock (3600s/day, timeSinceStartS), while the dossier's trade/civics/progression days come off the exporter CSVs on a different calendar (Time / 86400). Feeding exporter days into that helper would render every day 24× too large. So rather than force a wrong reuse or fork the name, I kept their world-clock formatDayHour untouched and named mine formatEventDay, with a note on both explaining the two calendars and flagging reconciliation as a follow-up for the sweep. That divergence (3600 vs 86400 seconds-per-day across the same game's data) feels like the real latent issue worth a dedicated ticket.

Fairly confident: 94 frontend tests + 490 backend pass, tsc/eslint/precommit clean, and the summary logic is exercised with realistic fixtures including the degrade-when-spine-missing path. Rough edge: the "selling/buying now" list is only as complete as the logistics board's capped offer rows, so a user's non-top offers may not show — acceptable for a glance view, but noted.

WARD-OUTCOME: done - `/users` listing removed, dossier leads with an actionable summary, all day floats now render `Day D, HH:MM`; test+lint+build+precommit green, landed on main. Mostly smooth, with one genuine surprise at the very end. The removals and the day+hour fix were clean, and wiring the actionable "At a glance" panel from the same logistics/stores spine `/trade` uses fell out naturally — owner-matched live offers, top specialties × current supply gaps, and recent trades in relative time, all best-effort so a missing exporter just thins the summary instead of sinking the page. The fight was the merge. A parallel run had already landed a *shared* `formatDayHour` on main — the "site-wide polish ticket" formatter the issue pointed at — but it's the **/info world clock** (3600s/day, `timeSinceStartS`), while the dossier's trade/civics/progression days come off the exporter CSVs on a **different** calendar (`Time / 86400`). Feeding exporter days into that helper would render every day 24× too large. So rather than force a wrong reuse or fork the name, I kept their world-clock `formatDayHour` untouched and named mine `formatEventDay`, with a note on both explaining the two calendars and flagging reconciliation as a follow-up for the sweep. That divergence (3600 vs 86400 seconds-per-day across the same game's data) feels like the real latent issue worth a dedicated ticket. Fairly confident: 94 frontend tests + 490 backend pass, tsc/eslint/precommit clean, and the summary logic is exercised with realistic fixtures including the degrade-when-spine-missing path. Rough edge: the "selling/buying now" list is only as complete as the logistics board's capped offer rows, so a user's non-top offers may not show — acceptable for a glance view, but noted.

coilysiren referenced this issue

2026-07-07 06:42:33 +00:00

Item surfaces overhaul: actionable per-item page (reverse-chrono feed, compress repeats, pagination, search, filters) + directory sort/hide-untraded #92

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-gaming/eco-app#93

No description provided.

Rows
Columns

User surfaces: actionable dossier + fix day-as-float / add hour + remove the all-users listing (closes #86) #93

Remove the all-users listing (/users)

Fix "day as a float" and add the hour (frontend/src/pages/User.tsx)

Make the dossier actionable for that specific player

Done when

Remove the all-users listing (`/users`)

Fix "day as a float" and add the hour (`frontend/src/pages/User.tsx`)