Reference creatortrack forge workspace id

Justin's CreatorTrack account has a dedicated workspace named "Forge / Creator Track", id 90, slug forge-creator-track-mrgi0bir. This is the intended target workspace for the Forge dev-queue / API-token-scoping build (task primitives, dev-queue skill, chat.justin dev_queue modifier) described in creatortrack-dev-tool-primitives-tokens-forge-bridge-2026-07-11.

A working ctk_ token already exists in ~/.forge-secrets/creatortrack-bot.env (env var CREATORTRACK_API_TOKEN). Today it is legacy full-access: GET /api/tasks and similar aggregate across ALL of Justin's workspaces (Personal/67, Gus The Bass/85, krystal playground/77, Test/78, Forge / Creator Track/90). Any dev-queue or Forge-client code built before the feat/api-token-scoping branch deploys must explicitly filter/pass workspace_id=90 to avoid touching other workspaces. After that branch merges + migrates + restarts, the token should be re-minted scoped to workspace 90 only.

Workspace list endpoint: GET /api/workspace/list.

Why: this pins the exact target so any future agent (or this one) building the dev-queue skill, Forge client, or chat.justin integration doesn't have to re-discover the workspace id or re-verify token scope. How to apply: when building/extending CreatorTrack dev-agent tooling (Forge client, dev-queue skill, chat.justin modifier), always target workspace 90 explicitly until token scoping ships; check reference_creatortrack_api_token_scopes.md for scoping deploy status before assuming least-privilege is in effect.

[auto-memory session 5ae6d8f3-bf72-464a-a2e8-61cf3b7368cf, confidence 0.85, mode direct]