Upload request card

UsageCopy Anchor Link

import { UploadRequestCard } from '@commenda/pathfinder/upload-request-card';

<UploadRequestCard
  key={request.id}
  title="Upload the signed documents"
  uploadConfig={{ accept: '.pdf', onFilesSelected: validateAndUpload }}
  attachmentConfig={{
    items: attachments,
    onRemove: removeAttachment,
    onRetry: retryUpload,
  }}
  onSubmit={submitDocumentIds}
/>;

Share an upload linkCopy Anchor Link

Inline requestCopy Anchor Link

Failure and retryCopy Anchor Link

LoadingCopy Anchor Link

Reset restores the example. Simulate failure retains the card for retry; no backend request is made.

API referenceCopy Anchor Link

Shared request propsCopy Anchor Link

RequestHandler<T> returns { status: 'accepted', recap: ResponseRecapProps } or { status: 'failed', message: string }, directly or as a Promise. A thrown error shows a retry message and preserves the draft. The host persists accepted responses; the component displays the returned receipt. state={{ status: 'resolved', recap }} restores history. Use a stable request ID as the React key, and change the key when the request changes. External pending is a rendering state; authorization and idempotency remain server responsibilities.

REQUEST-01: Docked tray uses pearl100, a raised shadow, radius16 and a white radius10 inset with 16px padding. Header40, footer at least44; controls wrap on narrow screens.

REQUEST-02: The parent places the request 12px above Composer at the same width. Inline requests are flat and fill their message column. Escape only temporarily dismisses; no global listener is installed.

REQUEST-03: Reading content does not animate. Existing Button and Popover motion respects reduced motion. Pending retains the draft and exposes a polite status. Acceptance never precedes the host result.

Design rulesCopy Anchor Link

• UPLOAD-REQUEST-01: The dropzone is at least 120px high, radius8, dashed pearl400. Existing AttachmentGroup renders files and overflow.
• UPLOAD-REQUEST-02: Send documents requires at least one file and every upload ready. Failed, uploading, and folder items block submission. Removing/retrying is blocked while submitting.
• UPLOAD-REQUEST-03: Selecting or dropping files never resolves the request. The host validates size/type/count, uploads, handles retries and cancellation, and returns stable IDs. accept is a browser hint, not validation; validate on the server too.

Pathfinder currently has no standalone FileUpload, so this phase adds a private native picker/dropzone rather than importing a private Kakashi runtime dependency. The demo keeps files in memory and makes no network request. Production code must mark them uploading until the server accepts them.

Integration and accessibilityCopy Anchor Link

Buttons have explicit names and keyboard focus. No network transport or AI SDK provider is required. Requests, tool execution, permission checks, durable outcomes and composer coordination stay in the application. See AI content integration for migration mappings; application migration is outside this build.