The stream view: /asked shows the owner's thoughts newest first, each with where it went and its state #653

Pillar: P7 Steering (#593), linked to the alignment work (#610-#615). First wave. One run, fresh from main.

Why. The owner: "the continuous thought that I am relaying is how this will work, so you and the forge need to be built for it." He steers by streaming thoughts, mid-flight, sometimes repeating or reversing earlier ones. Nothing may be lost or mangled.

Outcome. The owner sees every thought he has sent, newest first, each with where it went and whether it is placed, building, shipped or superseded, so he can see that nothing was lost; a thought with nothing built after N days is flagged.

Today. #611 builds /asked from issues people opened; thoughts are not there.

The path: the owner wonders whether something he said was heard; he opens /asked from the feed's header; primary action open the oldest flagged thought; next its placed issue.

Acceptance.

• [ ] /asked gains the thought stream (the same page, not a second one): verbatim text, time, source, placement links, state derived from the placed issues and their pulls.
• [ ] Flag: nothing merged N days after placement (N = 3 by default, a setting).
• [ ] Superseded thoughts show what superseded them.
• [ ] Minimal, not bare: one primary next action; the pull's looks show the path at phone and desktop widths and say what it removes.

Done means reachable:

• Page: /asked
• MCP: asked returns the thoughts with state
• Test: states derive correctly; flag after N days; superseded shown
• Look: the stream with each state

Removes: nothing; this is #611's page, extended.

Start from: the /asked page from #611, src/core/issues.ts, src/core/pulls.ts.

Depends on: #651, #611.

Must not touch: the release workflow, the chart, other repositories.