[jonbeckman]

AI Search can use built-in storage without an external-storage service token. This change makes that the source contract for new instances and sends documents through the namespace binding's Items API.

Administrators can upload, list indexing status, and delete documents. The new Upload to AI Search workflow node ingests text or JSON with administrator-owner authorization. Deployment configuration, Worker bindings, Actions workflows, and the secret-sync helper no longer require the external-storage token ID.

This is a breaking source transition. Existing R2/website records remain visible and exportable with a migration-required state, while retrieval excludes them. The legacy content bucket and existing artifact/skill storage remain available. docs/ai-search.md defines the staged copy, verification, reference switch, and retirement procedure; deployment does not convert or discard legacy content.

Validation:

• 31 account-free configuration, migration, storage-transfer, routing, and AI Search contract checks passed.
• The isolated live API check passed creation, upload, indexing, MCP retrieval, deletion with retrieval removal, workflow ingestion/retrieval, and rejection of unauthenticated/malformed uploads.
• The separate live browser check passed source creation, persisted built-in configuration, and opening the Documents/upload panel.
• Every attempt's owned namespace pair was removed and absence verified; earlier failed/interrupted attempts remain recorded as such.
• Root typecheck, lint, format, config:check, and build passed. kjanat/actionlint passed for the changed workflows.

The live launcher creates a unique isolated profile and uses Alchemy's native remote namespace binding. Ordinary local development keeps that binding disabled unless deployment.aiSearchEnabledInDev is selected explicitly.

This remains a draft pending review and recorded-action refresh. The complete core/external suite, an authenticated ordinary-member role check, historical-source transfer, and standing pre/prod deployment are separate unverified gates. No standing stage was deployed and no existing application data was migrated.