Store API

Takosumi can use any TCS 2.0-compatible Store as a Capsule discovery surface. The Store project, not Takosumi, owns the TCS wire contract. Consult the TCS 2.0 specification for canonical fields, routes, pagination, and error envelopes, and the Takosumi Store reference implementation for a working server. This page defines only Takosumi's integration boundary.

Install handoff

The only install authority Takosumi accepts from a TCS 2.0 listing is its Git repository URL. A suggested name and presentation metadata may initialize the UI, but they do not select executable content.

1. The dashboard receives the listing's repository URL.
2. Takosumi syncs a Source from that repository root and pins its ref to an immutable commit.
3. Takosumi obtains module candidates and provider requirements from the exact SourceSnapshot's tracked OpenTofu file scan. It auto-selects exactly one candidate and asks the user to select when multiple candidates exist.
4. The server uniquely resolves a host policy override matching the repository URL. When none exists, it uses the generic Git InstallConfig and checks the exact module within that policy ceiling.
5. It persists the selected module path in a Workspace-scoped derived InstallConfig and continues through the ordinary review, Plan, and Apply flow.

A Store client cannot send modulePath or installConfigId when requesting compileInstallUx: true. Zero candidates cannot be installed, exactly one is auto-selected, and multiple candidates require an exact dashboard choice. Multiple host overrides also fail closed; zero overrides use the generic host policy, so installing an app does not require registering an app-specific InstallConfig in the Store. A host override is execution policy matched by sourceSelector.url; it does not need store presentation metadata. Operator policy that permits lifecycle or credential use therefore cannot surface as a second Store listing.

Authority boundary

A Store listing and .well-known/tcs.json are discovery and presentation metadata. They have no authority to:

• select a module path, ref, tag, commit, SourceSnapshot, or InstallConfig;
• declare inputs, secrets, credentials, providers, Interface grants, or lifecycle policy; or
• proxy, cache, merge, or override .well-known/takosumi.json.

Takosumi ignores any path retained by a legacy response or presentation document when selecting a module. Switching Store nodes does not change the authority of an existing Capsule, Source, InstallConfig, Plan, or Run.

Discovery and local search

The required Store discovery interface is limited to server info, paginated listings, and listing detail. The dashboard searches presentation metadata from already fetched listings locally and does not call the reserved TCS 2.0 /tcs/v2/listings/search route. When more pages remain, Load more expands the local search set.

An unavailable server-side search must therefore never make the Store, Git repository discovery, or the Add action unavailable. The Store exists to discover Git URLs, not to provide a search index or installation policy.

Third-party Stores

A third-party Store works by implementing the TCS 2.0 read contract; it does not need Takosumi-specific install fields. Listing endpoints must be reachable by the browser, and repository URLs remain subject to Takosumi's Source policy. Authentication, moderation, and publishing belong to each Store and do not grant Takosumi Workspace authority.