Vendure Tokens

Keep component code semantic while applying the correct token-ownership mode for the current host.

Classify token ownership

Inspect git remotes and the task-local code.

1. Parse the owner from the origin and upstream git remotes. Treat the repository as Vendure-owned when either GitHub owner is exactly vendurehq, case-insensitively.
2. Treat code as a Dashboard extension when it imports or calls defineDashboardExtension from @vendure/dashboard, or when a VendurePlugin declares a dashboard entry.
3. Apply one mode:
   • Vendure-owned repository: consume all published token values without redefining them.
   • Dashboard extension: inherit the host dashboard theme without redefining token values, regardless of repository owner.
   • Standalone external app: preserve the semantic contract, but allow deliberate remapping of slot values and locally namespaced semantic slots.
4. If remotes are absent or ambiguous and no extension evidence exists, use standalone external behavior rather than claiming Vendure ownership.

Complete classification when one mode is selected from evidence.

Apply the semantic color invariant