Update to Hey-Traders! Quant Trading

Changed files

.codex-plugin/assets/composer-icon.png →

.codex-plugin/assets/logo.png →

.codex-plugin/plugin.json →

skills/heytraders-browser/SKILL.md →

skills/heytraders-browser/references/command-reference.md →

skills/heytraders-browser/references/runtime-contract.md →

skills/heytraders-browser/scripts/heytraders-cli.mjs →

skills/heytraders-browser/references/runtime-contract.md

--- before
+++ after
@@ -11,19 +11,23 @@
 
 The plugin must not duplicate any of these registries.
 
+## Plugin entry
+
+New product or sign-in tabs use `https://hey-traders.com/?ht_client=codex`. An existing canonical tab keeps its current URL, including workspace parameters and fragment. The adapter only dispatches commands; it does not reload the tab, add client fields to command arguments, or rewrite marketing UTMs. The entry marker is an untrusted client observation processed by the application's consent-aware acquisition owner, not identity or authorization evidence. An untagged reused tab does not establish a new Codex acquisition observation.
+
 ## Public plugin scope
 
 The public plugin uses the generic request router only for navigation, documentation, read-only market and account information, chart operations, backtests, and strategies whose described request and returned mode are explicitly simulated paper. Runtime discovery does not authorize real orders, live-mode strategies, exchange or wallet connection, credentials, or venue permissions. A historical command name that contains `live` does not expand this boundary: the command is usable only when its contract requires an explicit mode and the call is fixed to `paper`. The skill must stop when an operation's effect or mode is ambiguous.
 
 ## Discovery and readiness
 
-Use live `help` and `describe` when the selected command's current contract is unknown, stale, or rejected by schema validation. Reuse current contracts already available in the task. Readiness, route requirements, identifiers, and follow-up discovery are all returned by the application; the plugin does not maintain a parallel domain or route registry.
+Use live `help list` and `help describe` when the selected command's current contract is unknown, stale, or rejected by schema validation. Reuse current contracts already available in the task. Readiness, route requirements, identifiers, and follow-up discovery are all returned by the application; the plugin does not maintain a parallel domain or route registry.
 
 When an operation requires user action, the user owns the visible UI step. Rediscover state after the user confirms completion rather than treating navigation or dialog closure as success.
 
 ## Compatibility
 
-Facade version 5 exposes only metadata plus `window.__bridge.request`. Both the WebMCP tool and bundled Browser adapter use that entrypoint. The adapter requires a numeric safe-integer version of at least 5; missing, nonnumeric, fractional, and infinite versions fail closed. The plugin must not probe or call removed flat aliases.
+Facade version 7 uses domain-prefixed command selectors and result actions. Both the WebMCP tool and bundled Browser adapter use `window.__bridge.request`. The adapter requires a numeric safe-integer version of at least 7; missing, nonnumeric, fractional, and infinite versions fail closed. The plugin must not probe or call removed flat aliases.
 
 The installed adapter accepts only the canonical `https://hey-traders.com` origin, decodes command payloads as UTF-8, and returns structured bridge errors without falling back to legacy flat members.