@topolo/sdk 0.10.5 → 0.11.0

package/README.md

@@ -111,13 +111,11 @@ credential-scoped registry is the source of truth:
   id, slug, or name — including apps registered after this package was built.
 - `friendlyAppId(entry)` derives the display id from a live catalog entry.
 
-`DEFAULT_APP_URLS` now contains ONLY the `auth` and `developers` bootstrap
-seeds — the endpoints that must be reachable before the registry can be
-consulted. `APPLICATIONS` remains as a frozen static fallback snapshot used
-only when the registry is unreachable (it can enrich repo/deploy metadata for
-registry-confirmed apps, but never gates or rejects a registry-known app).
-`listBundledServices()` reads that snapshot and is deprecated for anything
-behavior-deciding.
+`DEFAULT_APP_URLS` contains only the `auth` and `developers` bootstrap seeds —
+the endpoints required before the registry can be consulted. If live discovery
+is unavailable, directory APIs fail closed with
+`application_catalog_unavailable`; the public SDK never substitutes compiled
+first-party metadata.
 
 ## Action catalog
 
@@ -148,16 +146,6 @@ the same authorization and confirmation path as `callAction()`.
 other transports that already hold canonical base64. `completionInput` supplies
 any additional fields required by a declared URL-session completion action.
 
-`APPLICATION_REQUIREMENTS` is the versioned app-build contract agents should
-read before creating or expanding a Topolo app. `requirementsForApplication()`
-filters the shared contract to the browser/API/tooling scopes implied by the app
-catalog entry.
-
-`auditApplicationRequirements()` and `auditAllApplicationRequirements()` turn
-that contract into catalog-backed conformance reports and migration-queue items.
-Catalog-visible evidence is marked directly; implementation details that require
-code or docs inspection are deliberately marked `needs_review`.
-
 ## Native dashboard widgets
 
 Launchable first-party applications populate the TopoloOne live workspace through