Record absolute-path metadata (displayText, resolvedPath, fingerprint,
start/end range) when a comment @-mention is captured, and validate it
at submit time with captureCommentMentions / resolveCommentMentions.

Free-text @mentions without metadata return [] from resolveCommentMentions
(no fallback re-resolve), preventing silent same-name cross-workspace
file attachment when a portable draft moves between workspaces.

- mention-metadata.ts: new pure module implementing capture + resolve
- prompt.tsx: FileContextItem gains optional resolvedMentions field
- build-request-parts.ts: remove parseCommentMentions, switch to
  resolveCommentMentions; ContextFile gains resolvedMentions field
- build-request-parts.test.ts: update existing @mention test to supply
  resolvedMentions; add cross-workspace and no-metadata drop tests

Replace the single global Persist.global history store with a per-directory
LRU cache (max 12 entries). Each directory gets its own Persist.workspace
storage for normal and shell history. No legacy keys are passed, so old
global history is ignored per v7 spec.

- history-store-factory.ts: extracted factory (Persist.workspace, no legacy keys)
- history-navigation.ts: LRU cache + ensureStores(); history/shellHistory become
  () => HistoryStore accessors; directoryToken signal + createEffect resets
  historyIndex/-1 and savedPrompt/null on directory change; rAF stale guard
  compares captured token before writing to DOM
- history-navigation.test.ts: 6 unit tests verifying Persist.workspace target
  shape, storage isolation per directory, key isolation per mode, no legacy keys

Replace the broad cross-directory draft-carryover snapshot with a
route-aware portable homepage runtime owner (design v7).

Key changes:
- portable-draft.ts: new PortableDraftOwner factory (runtime-only Solid
  signal, not persisted). Holds at most one snapshot per app run, keyed
  by sourceFilesystemDirectory. Implements record / consumeForHomepage /
  hide / restore / clear with revision-guarded stale-clear protection.
- portable-draft.test.ts: 17 unit tests covering record semantics
  (deep-equal no-bump, empty clears, per-field revision bumps),
  consumeForHomepage (self-move guard, non-empty target guard, move+bump),
  and clear (stale-revision guard, already-cleared returns true).
- draft-carryover.ts: replaced with a thin backwards-compat shim that
  re-exports usePortableDraft() from portable-draft.ts.
- draft-carryover.test.ts: rewritten as integration scenarios exercising
  v7 semantics (A→B move, self-move guard, non-empty guard, empty clears).
- editor-input.ts: carry-over createEffect now tracks params.id so it
  runs only on homepage routes (sessionID undefined). Session routes call
  portable.hide(). recordDraftEdit replaced with portable.record() on
  homepage routes only; session routes do not mirror. Text hydration on
  consume extracts text parts only — context+image hydration deferred to T5.

No stray consumers of recordDraftEdit/consumeCarryOver/clearCarryOver remain.

Introduce PinnedDraftOwner (pinned-draft.ts) that binds a deep-link
prefill prompt exclusively to its source directory. Unlike the portable
owner which floats between homepages, the pinned slot stays directory-
bound until release() or clearAll(expectedRevision) is called.

- adopt() creates/replaces the slot (revision 1); only called from
  the deep-link handler in layout.tsx.
- recordEdit() updates slot content without releasing it; empty content
  keeps the slot alive so typing fresh text remains pinned-scope.
- clearAll(rev?) / release() destroy the slot; clearAll returns false
  on stale revision for submit-lifecycle guards (T7).
- editor-input.ts checks pinned BEFORE portable in the homepage-carry
  effect: if pinnedSlot.directory === dir, project its content and skip
  portable consumption. handleInput routes edits to pinned (when slot
  matches) or portable (otherwise).
- layout.tsx handleDeepLinks calls pinned.adopt() for link.prompt so
  the prefill is directory-scoped from the moment the deep-link lands.

16 tests in pinned-draft.test.ts; all 84 prompt-input tests pass; typecheck clean.

On first boot after upgrading to v7, migrates the current workspace's
legacy route-scoped homepage draft (workspace:prompt) into the portable
runtime owner, then quarantines the source slot so future portable carries
are not clobbered. Sets a global sentinel (prompt-portable-migration) to
complete so the migration runs only once. On any failure the sentinel stays
non-complete and the migration retries on next boot.

PR1 scope: only the currently-opened directory is handled. Other workspaces'
drafts remain in their route-scoped stores and self-heal through subsequent
record() calls when the user visits those homepages.

…pty check

detectSubmitOwnership() reads pinned.current() and portable.snapshot()
to freeze the revision used by confirmOwnerCleared. Running it after
worktree/session create awaits captured the revision AFTER a user's
mid-await typing, then cleared the owner under that bumped revision —
wiping the new typing.

Move the detection next to the other pre-await captures so the revision
matches submit-time state.

onMount fires once at boot, before currentDir() is populated by the
autoselect pass, so the migration silently skipped for the whole
session. Convert to a createEffect with a one-shot started flag so the
migration runs as soon as a directory becomes available; runHomepage
Migration is already idempotent via the sentinel.

isUnderDirectory previously returned false for directories with a
trailing separator and for the POSIX root '/'. compactFilePath returned
an empty label when the path exactly matched the source directory,
rendering an unlabelled chip. Trim trailing separators before comparing,
treat empty as root, recognise forward-slash UNC, and fall back to the
directory basename when the strip leaves no remainder.

build-request-parts now drives comment file attachments off
item.resolvedMentions, but the real comment producers — file-tabs.tsx
addCommentToContext/updateCommentInContext and the createSessionCommentContext
controller used by review comments — never invoked captureCommentMentions.
Production submits silently dropped every @src/foo.ts in a comment body.

Run captureCommentMentions against sdk.directory on add and recapture on
every update so deleted mentions clear stale metadata, and plumb the source
filesystem directory accessor into createSessionCommentContext.

Adds tests that the real add path writes resolvedMentions and that an
update with no mentions overwrites stale ones with an empty array.

…eplay

ArrowUp recall calls replaceComments with PromptHistoryComment entries that
previously dropped resolvedMentions, so a history-replayed comment with
@src/foo.ts no longer attached the mentioned file.

Carry resolvedMentions through PromptHistoryComment, clonePromptHistoryComments,
historyComments(), and applyHistoryComments so recall produces the same
file parts the original submit would have.

…ubmit

CommentItem and restoreCommentItems lost resolvedMentions on the route
fallback path, so a failed submit followed by a retry would silently drop
metadata-backed @mentions from the rebuilt comments. Pass the field
through so buildRequestParts still emits the mentioned file parts.

The chip wrapper had aria-disabled="true" for external chips, but the
inner remove button stays fully operable. Advertising the container as
disabled gave assistive tech a state that conflicted with the button's
behaviour. The visual styling (cursor-not-allowed, dimmed opacity, the
External tooltip prefix) already communicates the disabled chip-action
state without misleading screen readers.

The test description claimed 'at most one resolves' but never enforced
the bound. A sloppy implementation that returned both same-name matches
would still pass. Add an explicit length cap.