Companion build queue — v0.4 amendment instructions — v0.1

Document: loomworks-companion-build-queue-v0_4-amendment-v0_1 Version: v0.1 (amendment-instruction document; the product is queue v0.4) Date: 2026-06-28 For: Claude Code — apply these splices to loomworks-companion-build-queue-v0_3.md and save the result as loomworks-companion-build-queue-v0_4.md (add-new-file; v0.3 stays a standing sibling per discovery-trajectory discipline). Purpose: Record that the mobile Companion surface landed (resolving the v0.3 open gap "mobile in-engagement transcript — confirm intended end state"), and add the three still-open Companion directions filed 2026-06-27/28 so the single canonical queue reflects current state.

Plain-language summary

The v0.3 queue listed "mobile in-engagement transcript — confirm intended end state" as an open gap. That's now built and pushed — the Companion is a readable fifth swipe surface on mobile. This bumps the queue to v0.4: marks that gap resolved, adds the mobile surface to the landed list, and records the three Companion directions (discoverability, conversation-search, recordable-facts) that were filed but aren't yet in the queue.

How to apply

Splice list against v0.3. Apply in order, update version/date header and footer (v0.3 → v0.4, date 2026-06-28).

Splice 1 — Header

• Version. v0.3 → Version. v0.4
• Date. 2026-06-27 → Date. 2026-06-28

Add a v0.4 change log line immediately under the existing v0.3 change log — RECONCILIATION. block:

> v0.4 change log. Marks the mobile Companion surface LANDED (resolving the v0.3 "mobile in-engagement transcript" open gap — the Companion is now a fifth swipe surface, slot 0, default landing; CR cr-mobile-companion-surface-v0_1, OL feat-companion-surface dac9fec). Adds the three open Companion directions filed 2026-06-27/28 (discoverability, conversation-search, recordable-facts/topic) to the queue's visible order. v0.3 preserved per discovery-trajectory discipline.

Splice 2 — Landed list — add item 8

In the ### ✅ Landed list, after item 7 ("Nav loop"), add:

> 8. Mobile Companion surface (fifth swipe surface) — the Companion is now a readable, persistent surface in the mobile swipe plane (slot 0, default landing on entering an engagement), alongside the four rooms. Renders the same transcript the desktop pane renders via a shared ConversationTranscript extraction (provenance carries to mobile — the cross-cutting conformance check below). Five-second hint flash unchanged. Frontend only. OL dac9fec on feat-companion-surface (pushed); CR cr-mobile-companion-surface-v0_1 in loomworks-record. Suite 443/83.

Splice 3 — Open gaps — resolve the mobile-transcript entry

In ## Open gaps / follow-ons, change the line:

> - Mobile in-engagement transcript — per mockup 2 there is no conversation transcript; replies surface transiently in the hint line. Confirm intended end state.

to:

> - Mobile in-engagement transcript — ✅ RESOLVED (mobile Companion surface, landed item 8). The intended end state was confirmed and built: the Companion is a fifth swipe surface (slot 0, default landing) rendering the persistent transcript; the transient hint flash stays alongside it. Scoping note loomworks-mobile-companion-surface-scoping-note-v0_1; CR cr-mobile-companion-surface-v0_1.

Splice 4 — Running queue table — add the three open Companion directions

The v0.3 running-queue table has items 1–4 (list-loading pagination; conversation-content fix; folder upload; loading states). Add three rows for the directions filed 2026-06-27/28. Append to the table:

> | 5 | Command/settings discoverability | Queued — own piece | "show settings" command + Preferences panel; plain-terms, generated from the real catalog (KNOWN_SETTINGS/_LABEL_TO_KEY). Lean: both, command-first. Do NOT fold into add-side. May share a catalog mechanism with the queued API-documentation effort. Scoping note loomworks-command-settings-discoverability-scoping-note-v0_1. | > | 6 | Conversation search | Queued — own piece | Find a past Companion exchange without re-asking; distinct from recall (recall = committed assertions; this = the message stream). Data already present (paginated keyset stream). Lean: deterministic text search first, engagement-scoped, results in place. Mobile-results dependency CLEARED (mobile surface landed, item 8). Scoping note loomworks-conversation-search-scoping-note-v0_1. | > | 7 | Recordable facts & topic | Investigation — design question, not yet buildable | The "it is sunny" probe: durable vs. ephemeral facts (does the system distinguish them), and whether assertions carry a topic so recall/removal work by subject not literal token/stem ("weather"↔"sunny", which stemming can't close). Touches the thesis. Settle the design before any build. Investigation loomworks-recordable-facts-and-topic-investigation-v0_1. |

Splice 5 — Footer

• Companion build — running queue + cross-cutting concerns — v0_3 — 2026-06-27 → Companion build — running queue + cross-cutting concerns — v0_4 — 2026-06-28

Verification checklist for CC after applying

• Header version/date = v0.4 / 2026-06-28; footer matches; v0.4 change-log line present.
• Saved filename = loomworks-companion-build-queue-v0_4.md (new sibling; v0.3 untouched and present).
• Landed list carries item 8 (mobile Companion surface).
• The mobile-transcript open-gap line reads RESOLVED.
• Running-queue table carries rows 5, 6, 7.
• No cross-cutting-concern content (trust-boundary, provenance display, grant-gating) altered — carries forward verbatim.

DUNIN7 — Done In Seven LLC — Miami, Florida Companion build queue — v0.4 amendment instructions — v0.1 — 2026-06-28 Splice list to turn v0.3 into v0.4: marks the mobile Companion surface landed (resolving the mobile-transcript gap), adds the three open Companion directions to the queue.