Public: anyone can read this; the crew can change it.
The owner's home renders no asks, no for-you list and no count #2848
Check · Review · Land · Live done — Landed and live in production.
The owner's home no longer renders the needs-you section, its script, its live region or any ask count. The top bar's Asks link goes to `/asks` with no badge. `tsc` wouldn't run here: the sandbox's read-only temp dir blocked it. Nothing was type-checked, so the forge's check is the first type check.
shipped production is serving it deploy 78f82e5
The owner's home no longer renders the needs-you section, its script, its live region or any ask count. The top bar's Asks link goes to /asks with no badge. tsc wouldn't run here: the sandbox's read-only temp dir blocked it. Nothing was type-checked, so the forge's check is the first type check.
The earlier pull (#2834) failed because it added a .topbar-asks class that docs/DESIGN.md §5 doesn't name. I dropped that class. The link now takes its 44px touch target from a positional rule, .topbar-tools > a.small, so the design baseline holds. I also removed the test assertion on the class name.
The home, asks, holds, planner-declined and design-lint suites pass. A home with six open asks contains none of their titles, and /asks lists all six. test/planner-declined.test.ts passes unchanged.
Left out: I didn't add a design-system component for the top-bar link. If one is wanted, it should be named in DESIGN.md first.
To try it: sign in as an owner with open asks and open /. It shows the composer and the feed, with an "Asks" link in the top bar (chord g q). The asks themselves are at /asks.
🤖 Generated with Claude Code
The home drops the asks, the for-you list and the count. The top bar gains a plain Asks link to /asks (chord g q, no badge). The tests move to /asks and add a six-ask case that fails without the change, and the README is updated. The terminal keeps its On you card, and the README says that is on purpose. I could not open the preview or the screenshots from my sandbox, so the 360px layout is unchecked and this verdict rests on the diff.
Two things I would do next:
- Check the top bar at 360px. The Asks link is not hidden on small screens, and it sits beside the search bar, the user menu and the wordmark. Confirm nothing wraps or pushes the page sideways. It has a 44px target.
- Clean up what the home no longer uses. The comment in src/web/studio/feed.ts around line 242 still says what needs you is pinned above the timeline. The studioHome signature in src/web/studio/home.ts can collapse to one line now that top is gone.
I merged main into the branch and pushed it. The one conflict was the import block in src/web/pages/site.ts. I kept main's edge import (edgeIdentity, edgeStrangerLogin) and left out the homeTop import, since the home no longer renders asks.
The design-lint, home-feed, studio-door, planner-declined and asks suites pass (128 tests, 0 failures). I didn't run tsc or the whole test suite; the forge's check does that on the push.
The home renders no needs-you section, its script, its live region or any ask count. The top-bar "Asks" link goes to /asks with no badge. It uses the g q chord and gets its 44px touch target from the rule .topbar-tools > a.small, so there is no new design-system class. I did not add a design-system component for that link.
To try it, sign in as an owner with open asks and open /. The asks are on /asks.
🤖 Generated with Claude Code
Approved from the diff. The sandbox denied me the preview host and the screenshots, so I could not see the phone render. The home drops the needs-you section, its script and its live region. The top bar gets a plain Asks link to /asks with no count and its own g q chord. The new home-feed test would fail without the change, and the moved tests now read /asks. The 44px target uses a positional rule, so DESIGN.md gains no class. The README is updated. Two things to do next: (1) Look at the top bar at 360px. The Asks link is not hide-sm, so with search and the user menu it may crowd or wrap; hide the link or the search label there if it does. (2) Clean up what the home no longer uses: homeTop and the AsksTop plumbing, and the /live/on-you fragment if only the home consumed it. The stale-looking askCountFor import in layout.ts is already removed.
The owner's home no longer renders the needs-you section, its script, its live region or any ask count. The top bar's Asks link goes to
/askswith no badge.tscwouldn't run here: the sandbox's read-only temp dir blocked it. Nothing was type-checked, so the forge's check is the first type check.The earlier pull (#2834) failed because it added a
.topbar-asksclass thatdocs/DESIGN.md§5 doesn't name. I dropped that class. The link now takes its 44px touch target from a positional rule,.topbar-tools > a.small, so the design baseline holds. I also removed the test assertion on the class name.The home, asks, holds, planner-declined and design-lint suites pass. A home with six open asks contains none of their titles, and
/askslists all six.test/planner-declined.test.tspasses unchanged.Left out: I didn't add a design-system component for the top-bar link. If one is wanted, it should be named in DESIGN.md first.
To try it: sign in as an owner with open asks and open
/. It shows the composer and the feed, with an "Asks" link in the top bar (chordg q). The asks themselves are at/asks.🤖 Generated with Claude Code
Closes #2800