The Conversations Activity hub page embeds the document at design/stories/conversations/give-always-context-to-comment-reply-thread (block _vIorYgk). That document was renamed to context-reply-thread on 2026-07-10. A redirect preserves link resolution, but the embed still references the stale path.

_Why:_ Embeds should point to canonical paths. Redirects add an unnecessary resolution hop. The embed title shown in the hub card reflects the old document name. Update the embed block to point to hm://z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno/design/stories/conversations/context-reply-thread.

The canonical Repository Maintenance document at /repository-maintenance remains in its truncated state from 2026-07-08. It contains only a note about the truncation, a link to the full version, and links to two weekly-check documents.

_Why:_ This was first reported on 2026-07-08 and flagged again on 2026-07-09. The full history at v=bafyreichub6haju4mka4xpugypqhbtz33oowlku5ftr6x2g3k24qfzwa2i should be restored as the document body, with the weekly-check sub-documents linked as appendices. The current state is misleading to anyone visiting directly.

The document title metadata now reads "Context to comment reply / thread" but the body's first line still says "Give always context to comment reply / thread chronology".

_Why:_ When a document is renamed, the body heading should match the new title to avoid confusion. The old heading text is visible to readers and contradicts the displayed title.

The Admin Settings user story had 5 revisions on 2026-07-10 between 15:19 and 16:10 UTC. Each revision replaced image blocks (design mockups) with iterative updates.

_Why:_ This is a team workflow observation, not a structural problem. However, version history hygiene benefits from fewer, more consolidated revisions. Consider drafting design iterations in a separate scratch document and publishing consolidated updates.

Already reported on 2026-07-09. The Design meetings Notes hub still has the July 8th meeting as a single paragraph under a heading rather than as an embedded child document. June 17th and June 29th meetings are embedded as separate documents.

_Why:_ Inconsistent structure. If the July 8th meeting had more substantive notes, a dedicated child document would be more appropriate. Even a thin document follows the established pattern.

The title text contains a double space: "As an Admin, I want to define main settings of my site" (note the two spaces between "want" and "to").

_Why:_ Double spaces in metadata titles affect exact-match search and display.

A substantive technical discussion about enabling CloudFlare proxy for the Seed web app is happening in comments on the Tech Talks document (thread started by Eric on 2026-07-09, with Burdi and the team responding). The discussion covers p2p traffic, SSH access, and the media vs non-media split.

_Why:_ If a decision is reached or a plan emerges, the outcome should be captured in a dedicated tech-talks child document. Comment threads are ephemeral and harder to reference later.