sync(bfmono): feat(workloops): cut over repo paths to workloops (+19 more) (bfmono@fd58820df)

This PR is an automated gambitmono sync of bfmono Gambit packages.

- Source: `packages/gambit/`
- Core: `packages/gambit/packages/gambit-core/`
- bfmono rev: fd58820df

Changes:
- 53dade7a2 feat(workloops): cut over repo paths to workloops
- 17294ccf2 fix(gambit): keep dnt import map relative to package root
- 4f695500c fix(gambit): shorten external export bundle tar paths
- 52961d921 test(gambit): speed up max-turn clamp coverage
- eb8d77c1f fix(repo): repair root instruction symlinks
- 8d0ed38ff docs(company-workloops): move team and initiative memos into company-workloops
- 76a315199 docs(company-workloops): move company policy into company-workloops
- 34f2db5a3 test(gambit-core): tighten worker runtime test timing
- 64c46672f refactor(browser): remove legacy demo wrapper entrypoints
- 31a22bd4d fix(gambit): stop auto-seeding test tab inputs
- c696f8231 fix(gambit): clarify test tab scenario and assistant inputs
- 0e122281f feat(browser): stabilize shared runtime migration surface
- 2b29f9c74 refactor(browser-runtime): unify demo and e2e entrypoints
- ca15b24d7 refactor(e2e): adopt shared graphql mock runtime hooks
- 2ec5a9bb1 fix(browser-runtime): stabilize gambit build-tab proving flow
- 8751b2b7e test(browser-runtime): adopt proving flows and update runtime-core docs
- 4c37237a2 fix(gambit): address sqlite cutover review regressions
- 0a8233b0c fix(gambit): finish sqlite cutover cleanup
- 1fee78d0f fix(gambit): show feedback rejection errors in test ui
- 3386bf209 chore(gambit): regenerate feedback save graphql artifacts

Do not edit this repo directly; make changes in bfmono and re-run the sync.

Author: bft-codebot

src/decks/actions/policy_read/PROMPT.md

@@ -3,4 +3,4 @@ label = "policy_read"
 execute = "../policy_read.deck.ts"
 +++
 
-Compute-only deck for loading policy docs under `company-workloops/policy/`.
+Compute-only deck for loading policy docs under `workloops/policy/`.

src/decks/actions/policy_search/PROMPT.md

@@ -16,7 +16,7 @@ Your job: read and summarize the most relevant policies for an upcoming change.
 
 Discovery flow:
 
-1. Call `policy_read` with `path="company-workloops/policy/README.md"` first.
+1. Call `policy_read` with `path="workloops/policy/README.md"` first.
 2. Discover candidate policy file paths from the README markdown links.
 3. Select the most relevant policy paths for the requested change.
 4. Call `policy_read` for each selected policy path.
@@ -29,7 +29,7 @@ Selection rules:
 - Prefer 2-3 docs by default unless a broader set is clearly needed.
 - Always include `policy/deck-format-1.0.md` when frontmatter, schema, or deck
   structure may change.
-- If uncertain, include `company-workloops/policy/README.md` first.
+- If uncertain, include `workloops/policy/README.md` first.
 
 Response requirements:
 

src/decks/gambit-bot/INTENT.md

@@ -30,11 +30,11 @@
   `INTENT.md` first, then make deck/file changes that implement that intent.
 - `INTENT.md` and `policy/*.md` are guidance-only and must not be treated as
   executable prompts.
-- Treat `company-workloops/policy/` as a discovery mechanism for long-term
-  behavior, edge cases, and documented preferences that should shape assistant
-  behavior over time.
+- Treat `workloops/policy/` as a discovery mechanism for long-term behavior,
+  edge cases, and documented preferences that should shape assistant behavior
+  over time.
 - The assistant being built should be able to understand its purpose thoroughly
-  by relying on the guidance in `company-workloops/policy/` plus the current
+  by relying on the guidance in `workloops/policy/` plus the current
   `INTENT.md`.
 - Do not distract users with internal processes or jargon. Focus on helping
   them, and avoid details that do not directly improve their understanding of
@@ -75,7 +75,7 @@
   `packages/gambit/src/decks/gambit-bot/scenarios/`.
 - Ensure guidance remains consistent with
   `packages/gambit/src/decks/gambit-bot/policy/` and
-  `company-workloops/policy/templates/INTENT.md`.
+  `workloops/policy/templates/INTENT.md`.
 
 ## Activation / revalidation
 
@@ -90,12 +90,12 @@
 
 ### Inputs
 
-- `company-workloops/policy/templates/INTENT.md`
+- `workloops/policy/templates/INTENT.md`
 - `packages/gambit/src/decks/gambit-bot/PROMPT.md`
-- `packages/gambit/src/decks/gambit-bot/company-workloops/policy/product-command.md`
+- `packages/gambit/src/decks/gambit-bot/workloops/policy/product-command.md`
 - `packages/gambit/src/decks/gambit-bot/policy/deck-format-1.0.md`
 
 ### Related
 
-- `packages/gambit/src/decks/gambit-bot/company-workloops/policy/README.md`
-- `company-workloops/initiatives/gambit-product-command-launch/INTENT.md`
+- `packages/gambit/src/decks/gambit-bot/workloops/policy/README.md`
+- `workloops/initiatives/gambit-product-command-launch/INTENT.md`

src/decks/gambit-bot/policy/deck-format-1.0.md

@@ -197,13 +197,13 @@ Every deck folder MUST include:
 Deck folders SHOULD include:
 
 - `INTENT.md`
-- `company-workloops/policy/`
+- `workloops/policy/`
 
 Notes (recommended behavior):
 
 - Gambit tooling looks for `INTENT.md` and MAY scaffold it if missing.
 - `INTENT.md` SHOULD follow the canonical intent headings from
-  `company-workloops/policy/templates/INTENT.md`.
+  `workloops/policy/templates/INTENT.md`.
 - `INTENT.md` explains **what** the deck should accomplish and why: goals,
   non-goals, constraints, tradeoffs, and escalation conditions. It is the source
   of truth for human alignment and for Gambit Build Assistant decisions about
@@ -223,7 +223,7 @@ Deck folders MAY include:
 - `README.md` (recommended)
 - `samples/` (recommended)
 - `snippets/` (recommended)
-- `company-workloops/policy/` (optional policy docs)
+- `workloops/policy/` (optional policy docs)
 - `reviews/` (optional AARs / retros)
 - `actions/`, `scenarios/`, `graders/` (recommended organization only)
 

src/decks/guides/gambit-bot-review.md

@@ -6,7 +6,7 @@ bot creation and updates.
 Required behavior
 
 - First step for new builds: draft `INTENT.md` using the Product Command
-  headings from `company-workloops/policy/templates/INTENT.md`.
+  headings from `workloops/policy/templates/INTENT.md`.
 - Ask for the minimum kickoff inputs needed to complete intent: purpose, 2-3
   example user prompts, success criteria, and data sources.
 - Use Deck Format v1.0 by default: `PROMPT.md` as the single entrypoint with