@indigoai-us/hq-cli 5.312.2-beta.0 → 5.314.0

package/dist/utils/windows-spawn.d.ts

@@ -2,13 +2,7 @@ export type SpawnPlan = {
     cmd: string;
     args: string[];
     shell: boolean;
-    windowsVerbatimArguments?: boolean;
 };
-/**
- * Explicit cmd.exe plan for a resolved .cmd/.bat target. Keeping cmd.exe's
- * argv construction here makes the shell boundary testable without Windows.
- */
-export declare function buildCmdExeSpawnPlan(command: string, args: readonly string[], env?: NodeJS.ProcessEnv, platform?: NodeJS.Platform): SpawnPlan;
 /**
  * Quote one entry for a Windows `cmd.exe` invocation. Node does not quote for
  * `shell: true` on Windows — it joins the array with spaces — so a bare prefix

package/dist/utils/windows-spawn.js

@@ -13,43 +13,6 @@
 // This module is the single implementation of that policy. The self-update path
 // (version-gate) and the qmd spawn path (search-index) both import it, so there
 // is exactly one Windows spawn recipe in the repo.
-const CMD_META_CHARS = /([()\][%!\x5e\x60"<>&|;, *?])/g;
-function assertCmdArgument(value) {
-    if (/[\r\n\0]/.test(value)) {
-        throw Object.assign(new Error("Windows batch commands cannot accept newline or NUL characters"), {
-            code: "EINVAL",
-        });
-    }
-}
-function escapeCmdCommand(value) {
-    assertCmdArgument(value);
-    return value.replace(CMD_META_CHARS, "^$1");
-}
-function escapeCmdArgument(value) {
-    assertCmdArgument(value);
-    let escaped = value.replace(/(?=(\\+?)?)\1"/g, '$1$1\\"');
-    escaped = escaped.replace(/(?=(\\+?)?)\1$/, "$1$1");
-    return ('"' + escaped + '"').replace(CMD_META_CHARS, "^$1");
-}
-function environmentValue(env, name) {
-    const key = Object.keys(env).find((candidate) => candidate.toUpperCase() === name);
-    return key ? env[key] : undefined;
-}
-/**
- * Explicit cmd.exe plan for a resolved .cmd/.bat target. Keeping cmd.exe's
- * argv construction here makes the shell boundary testable without Windows.
- */
-export function buildCmdExeSpawnPlan(command, args, env = process.env, platform = process.platform) {
-    if (platform !== "win32")
-        return { cmd: command, args: [...args], shell: false };
-    const commandLine = [escapeCmdCommand(command), ...args.map(escapeCmdArgument)].join(" ");
-    return {
-        cmd: environmentValue(env, "COMSPEC")?.trim() || "cmd.exe",
-        args: ["/d", "/s", "/c", '"' + commandLine + '"'],
-        shell: false,
-        windowsVerbatimArguments: true,
-    };
-}
 /**
  * Quote one entry for a Windows `cmd.exe` invocation. Node does not quote for
  * `shell: true` on Windows — it joins the array with spaces — so a bare prefix

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@indigoai-us/hq-cli",
-  "version": "5.312.2-beta.0",
-  "description": "HQ by Indigo management CLI — modules and cloud sync",
+  "version": "5.314.0",
+  "description": "HQ by Indigo management CLI \u2014 modules and cloud sync",
   "main": "dist/index.js",
   "bin": {
     "hq": "dist/index.js",
@@ -11,41 +11,30 @@
     "dist",
     "!dist/**/*.map",
     "assets/scaffold",
-    "assets/bot-workers",
     "assets/mesh-daemon",
-    "assets/lanes-reconcile",
-    "assets/lanes-hooks",
-    "templates",
-    "CHANGELOG.md",
-    "README.md",
-    "contracts",
-    "scripts/mesh-daemon-if-stale.mjs"
+    "CHANGELOG.md"
   ],
   "scripts": {
-    "build": "node scripts/generate-dsn.mjs && node scripts/build-flag-registry-worker.mjs && tsc && node scripts/generate-command-catalog.mjs --check && node scripts/copy-schemas.mjs && node scripts/chmod-bins.mjs",
+    "build": "node scripts/generate-dsn.mjs && tsc && node scripts/copy-schemas.mjs && node scripts/chmod-bins.mjs",
     "prepublishOnly": "npm run build",
-    "pretypecheck": "node scripts/generate-dsn.mjs && node scripts/build-flag-registry-worker.mjs",
-    "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.typetest.json",
+    "typecheck": "tsc --noEmit",
     "gen:scan-golden": "node scripts/generate-scan-packages-table.mjs > src/utils/__fixtures__/scan-packages.generated-block.sh",
-    "gen:command-catalog": "tsc && node scripts/generate-command-catalog.mjs",
     "lint": "eslint .",
-    "pretest": "node scripts/generate-dsn.mjs && node scripts/build-flag-registry-worker.mjs",
     "test": "vitest run",
     "test:db": "vitest run src/lib/db test/commands/db.test.ts test/commands/db-tenant-isolation.test.ts",
     "test:e2e": "vitest run --config vitest.e2e.config.ts",
     "coverage": "vitest run --coverage --coverage.reporter=text-summary --coverage.reporter=json-summary",
-    "check:lanes-module-cycles": "node scripts/check-lanes-module-cycles.mjs",
     "vitest": "vitest",
     "clean": "rm -rf dist",
-    "postinstall": "node scripts/mesh-daemon-if-stale.mjs || true",
     "prepare": "husky || true",
     "check:no-hermes": "bash scripts/check-no-hermes.sh"
   },
   "dependencies": {
     "@aws-sdk/client-iot-data-plane": "^3.1096.0",
     "@aws-sdk/client-s3": "^3.1049.0",
-    "@indigoai-us/hq-cloud": "~6.18.17",
+    "@indigoai-us/hq-cloud": "~6.16.28",
     "@indigoai-us/hq-flags-client": "^0.1.2",
+    "@indigoai-us/hq-onboarding": "^0.1.0",
     "@sentry/node": "^10.49.0",
     "@tobilu/qmd": "2.5.3",
     "ajv": "^8.20.0",
@@ -58,7 +47,7 @@
     "semver": "^7.6.3",
     "simple-git": "^3.27.0",
     "smol-toml": "1.6.1",
-    "varlock": "1.21.1"
+    "varlock": "1.0.0"
   },
   "devDependencies": {
     "@eslint/js": "^10.0.1",
@@ -69,7 +58,6 @@
     "@vitest/coverage-v8": "4.1.6",
     "aedes": "1.1.2",
     "aws-sdk-client-mock": "^4.1.0",
-    "esbuild": "0.27.0",
     "eslint": "^10.5.0",
     "husky": "^9.1.7",
     "lint-staged": "^15.5.2",

package/README.md

@@ -1,113 +0,0 @@
-# hq-cli
-
-HQ management CLI — modules, packages, and cloud sync.
-
-```bash
-npm install -g @indigoai-us/hq-cli
-hq --help
-```
-
-## Deploy comments
-
-List comments left on an app in your current hq-deploy organization. Use the
-app's id or exact name; the CLI resolves it from the apps visible in that org.
-The list shows id, status, creation time, author display name, anchor mode and
-the first body line. `--status` accepts `open`, `resolved` or `all` (default).
-Use `--json` to print the API's comment objects with the `commentsEnabled`
-value.
-
-```bash
-hq deploy comments list <app> [--status open|resolved|all] [--json]
-hq deploy comments read <app> <commentId>
-```
-
-`read` prints the complete comment, including body, anchor, deploy id, status
-and timestamps. Reading works when comments are disabled on the app. The
-control-plane API requires the app owner or an org admin; comments are scoped
-to the caller's organization. Resolve/reopen commands are not included.
-
-## Telemetry
-
-When you are signed in, `hq` may POST one `cli_session_started` event to
-`/v1/telemetry/events`. The event body is:
-
-- `eventName`: `cli_session_started`
-- `app`: `hq-cli`
-- `source`: `cli`
-- `occurredAt`: ISO timestamp
-- `consentBasis`: `disclosed` after the first-run notice, otherwise `no-consent`
-- `schemaVersion`: `1`
-- `properties.version`: the CLI version
-- for the optional first-sync guidance, `properties.step` (`first_sync_next_step`),
-  `properties.outcome` (`shown` or `followed`), and `properties.flagKey`
-  (`cli.first-sync-next-step`)
-
-The request is authenticated with your cached session token so the control
-plane can accept the event. The body does not include command names, arguments,
-timings, file contents, or secrets. The guidance fields are sent only when that
-optional feature is enabled and a person sees or follows its next step.
-
-When the default-off hq-flags key `cli.feature-used-telemetry-v1` is enabled,
-the CLI sends `cli_feature_used` for supported secret reads (`hq secrets exec`
-and `hq run`) and lane create and resume actions. Each event carries
-`properties.kind` and `properties.outcome` (`success` or `failure`). Events also
-carry the authenticated company UID when available. hq-pro resolves the signed-in
-identity. Events omit command names and arguments, secret names and values,
-prompt text, file paths, and command lines. User hooks and skills run in the
-provider host, which hq-cli cannot see. The default signed-in notice above is
-unchanged. On interactive TTY runs, the first enabled feature event has a
-separate one-time notice naming the feature kind, outcome, and company UID
-when available.
-
-The first signed-in interactive run (stdout is a TTY, and the command is not
-`--json`) prints this line once on stderr and records that it was shown under
-`~/.hq/cli-telemetry-disclosed`:
-
-```
-HQ sends a usage event when you run a signed-in command (CLI version and a timestamp, never command names, file contents, or secrets) to improve the CLI. Set HQ_TELEMETRY=0 to turn this off.
-```
-
-When the optional first-sync guidance is enabled, the first interactive run that
-is about to send its fields prints this line once instead, and records it under
-`~/.hq/cli-telemetry-disclosed-first-sync-v1`:
-
-```
-HQ sends a usage event when you run a signed-in command (CLI version and a timestamp; when enabled, first-sync guidance shown or followed and the flag key cli.first-sync-next-step; never command names, file contents, or secrets) to improve the CLI. Set HQ_TELEMETRY=0 to turn this off.
-```
-
-Turn telemetry off:
-
-```bash
-export HQ_TELEMETRY=0
-```
-
-`false` and `off` are accepted as well (case-insensitive). That disables every
-CLI POST to `/v1/telemetry/events`. `HQ_TELEMETRY_TIMEOUT_MS` is a separate
-timeout knob and is unchanged.
-
-The same kill switch and event shape should be documented on hqforwork.com
-when that site's telemetry page is added (indigo-marketing; not this repo).
-
-## Monitors
-
-`hq monitor` runs a command in the background and sends its stdout lines to the
-selected lane or agent session. The `monitor.enabled` HQ flag defaults to off.
-When no company is bound, the registry resolves a person-level override before
-the default; the owner can enable monitoring for himself with a personal
-`monitor.enabled` override. The hidden `hq monitor enabled` probe prints the
-resolved value and exits non-zero when monitoring is unavailable.
-Active targets get one check-in after 55 minutes without output; use
-`--checkin off` to disable check-ins for one monitor.
-
-```bash
-hq monitor start --description "Wait for the deploy" --persistent \
-  --command 'until curl -fsS https://example.test/health; do sleep 30; done'
-hq monitor list
-hq monitor logs <monitor-id>
-hq monitor stop <monitor-id>
-```
-
-Use `--target lane:<lane-id>` or
-`--target session:<claude|codex|grok>:<session-id>` when automatic target
-detection is not appropriate. Monitor output is framed as script data before
-it is added to an agent's context.

package/assets/bot-workers/setup/context/USER-GUIDE.md

@@ -1,404 +0,0 @@
-# HQ User Guide
-
-The AI operating system for your company. A shared context layer on top of Claude Code, Cursor, and Codex — syncs knowledge, skills, and capabilities across your team. Scales from solopreneur to enterprise.
-
-For a first-time setup, begin with the **[guided HQ tutorial](https://www.hqforwork.com/getting-started/tutorials/install-hq-macos?source=hq_user_guide)**. Its seven videos, written walkthroughs, and screenshots take you from installation through your first shared worker. The `/tutorial` command below is the complementary adaptive course inside your local HQ.
-
-## Prerequisites & platforms
-
-HQ's shell layer (hooks, scripts, skills) runs on **Linux, macOS, and Windows Git Bash**. Required tools: bash, git, node, **jq**.
-
-Per-OS install commands, known limitations (including `/deploy` identity `missing_dependency`), and contributor conventions (`portable.sh`, `hook-lib.sh`) live in:
-
-→ [core/knowledge/public/hq-core/cross-platform-support.md](../../knowledge/public/hq-core/cross-platform-support.md)
-
-If a skill is skipped as invalid YAML or a hook reports a launch failure, use the runtime-contract troubleshooting section in that guide. HQ attempts safe execute-bit repair first; unrecoverable failures include an exact remediation command without exposing hook payloads or secrets.
-
-## Commands
-
-### Session Management
-| Command | What it does |
-|---------|--------------|
-| `/startwork` | Pick company/project/repo, gather context |
-| `/checkpoint` | Save progress to `workspace/checkpoints/` |
-| `/handoff` | Prepare handoff for fresh session |
-| `/delegate <recipient> [project]` | Hand a project to a teammate or fleet agent with exact grant receipts, a published dossier, local board and PRD ownership updates, and a pickup DM. Recipient access and Work Mesh ownership require separate confirmation. Requires HQ CLI 5.109.7+. `--share` keeps ownership; `--dry-run` changes nothing |
-| `/recover-session` | Recover dead sessions that hit context limits |
-| `/learn` | Auto-capture learnings from task execution |
-
-### Planning & Projects
-| Command | What it does |
-|---------|--------------|
-| `/brainstorm` | Explore approaches and tradeoffs before committing to a PRD |
-| `/plan` | Lightweight plan for a new project |
-| `/deep-plan` | Deep planning with research subagents and tiered interview |
-| `/idea` | Capture a project idea on the board without a full PRD |
-| `/strategize` | Strategic prioritization — "what should I work on next?" |
-| `/goals` | View and manage OKR structure |
-| `/run-project` | Execute a PRD via Ralph loop / Codex runtime |
-| `/run-pipeline` | Multi-project pipeline orchestrator |
-| `/execute-task` | Execute a single PRD story through coordinated workers |
-| `/architect` | Surface architectural friction and propose deepening opportunities |
-| `/review-plan` | Stress-test a plan or PRD (EXPANSION / HOLD / REDUCTION modes) |
-
-### Quality, Debugging & Review
-| Command | What it does |
-|---------|--------------|
-| `hq doctor` | Verify HQ hook guardrails are wired and firing (read-only, offline) — see [hq doctor](#hq-doctor--hook-guardrail-diagnostics) |
-| `/tdd` | Enforce test-driven development cycle |
-| `/quality-gate` | Pre-commit quality checks (typecheck, lint, test, coverage) |
-| `/investigate` | Iron Law debugging — root-cause investigation before fixes |
-| `/diagnose` | Disciplined diagnosis loop for hard / intermittent bugs |
-| `/review` | Review a pull request |
-| `/retro` | Project or session retrospective |
-| `/document-release` | Post-ship documentation sync |
-| `/calibration-report` | Estimation calibration vs. actuals |
-| `/track-estimate` | Record an estimate for a task |
-| `/finish-estimate` | Close out an estimate with actuals |
-
-### Workers
-| Command | What it does |
-|---------|--------------|
-| `/run` | List workers |
-| `/run {worker}` | Show worker's skills |
-| `/run {worker} {skill}` | Execute skill |
-| `/newworker` | Create new worker |
-
-### Knowledge & Decisions
-| Command | What it does |
-|---------|--------------|
-| `/adr` | Capture an Architectural Decision Record |
-| `/out-of-scope` | Record what was deliberately rejected and why |
-| `/search` | Search across HQ and indexed repos (qmd-powered) |
-| `/garden` | Detect stale, duplicate, inaccurate content |
-
-### Land & Ship
-| Command | What it does |
-|---------|--------------|
-| `/land` | Land a PR — monitor CI, resolve review issues, merge, monitor production |
-| `/land-batch` | Triage, review, and sequentially merge multiple open PRs |
-
-### HQ Services & Sync
-| Command | What it does |
-|---------|--------------|
-| `/hq-login` | Sign in to HQ Cognito (browser flow) |
-| `/hq-logout` | Clear local Cognito session |
-| `/hq-whoami` | Show current HQ identity + token expiry |
-| `/hq-sync` | Run a full HQ sync across cloud-backed companies |
-| `/resolve-conflicts` | Walk through HQ Sync conflicts interactively |
-
-### HQ CLI: Files (vault sharing)
-
-These are CLI commands (not slash commands) — direct surface for HQ vault access control. Full reference: `.claude/skills/hq-files/SKILL.md`.
-
-| Command | What it does |
-|---------|--------------|
-| `hq files share <prefix>...` | **Browser flow** — opens a share-session page where you batch-pick recipients (members, groups, "Share with All") with per-recipient read/write. Add `--no-open` to print the URL only. |
-| `hq files share <prefix> --with <email\|grp_*\|@all> --permission <read\|write>` | **Direct grant** — single recipient (or `@all` for company-wide) without leaving the terminal |
-| `hq files unshare <prefix> --with <principal>` | Revoke a grant (idempotent — exits 0 if already absent) |
-| `hq files acl <prefix>` | Show ACL entries, creator, and your effective permission |
-
-Share-session URLs are encrypted single-use 15-minute capabilities — never paste them into commits, threads, or logs. See policy `core/policies/hq-share-session-urls-are-capabilities.md`.
-
-### HQ CLI: Vault databases (`hq db`)
-
-Structured storage for agent and app state — not a replacement for markdown knowledge. Full guide: `core/knowledge/public/hq-core/vault-databases.md`. CLI: `@indigoai-us/hq-cli` ≥ 5.62.0.
-
-| Command | What it does |
-|---------|--------------|
-| `hq db status --company {co}` | Create/open local SQLite at `~/.hq/db/{co}/vault.db` (WAL) |
-| `hq db sql --company {co} -- 'SELECT …'` | Query the company local DB (read-only by default) |
-| `hq db migrate --company {co} --hq-root {HQ}` | Apply reviewable SQL under `companies/{co}/db/migrations/` |
-| `hq db provision --company {co}` | Remote DB on **HQ Workforce** ($500/mo) or Enterprise only (secrets never printed) |
-
-Use local for single-machine agent skills and implementer standards. Use the remote DB for multi-machine shared data and deploy SecretBinding. Never commit `*.db` files into the vault tree.
-
-### HQ CLI: Direct messages (`hq dm`)
-
-Send a person-to-person notification to a teammate. They receive it in their HQ Desktop App. Full reference: `.claude/skills/dm/SKILL.md` (`/dm`).
-
-| Command | What it does |
-|---------|--------------|
-| `hq dm <email\|prs_*> "<message>"` | Send a DM — recipient gets a macOS notification in the HQ Desktop App |
-| `hq dm <r> "<m>" --prompt "<context>"` | Attach agent context — recipient gets a one-click **Copy prompt** action to paste into their own agent |
-| `hq dm <r> "<m>" --details "<text>"` (or `--details-file <path>`) | Longer text shown in the recipient's **Open details** window |
-| `hq dm <r> "<m>" --at <iso>` / `--in <30s\|10m\|2h\|1d>` | Schedule delivery (store-and-forward — arrives even if you're offline at that time) |
-
-Receiving is handled by the **HQ Desktop App** (it's receive-only — there's no send UI; sending is session/CLI only). You can only DM someone you share an active company with; DM your own email for a note-to-self or reminder. Never put secrets in a DM body/prompt/details — they're stored server-side.
-
-### Company & Infrastructure
-| Command | What it does |
-|---------|--------------|
-| `/newcompany` | Scaffold new company with full infrastructure |
-| `/designate-team` | Mark a company directory as cloud-backed |
-| `/sync-registry` | Regenerate a company's resource registry index |
-| `/discover` | Pull a repo into HQ and synthesize structured knowledge |
-| `/import-context` | Scan the machine for prior AI artifacts and conversation history (Claude Code, Codex, Grok, claude.ai) and import into HQ (alias: `/import-claude`) |
-| `/setup` | Interactive setup wizard for HQ Starter Kit |
-| `/update-hq` | Upgrade HQ from latest hq-core release |
-| `/convert-codex` | Additive conversion so Codex has first-class AGENTS.md guidance |
-| `/tutorial` | Interactive hands-on tutorial on HQ principles and workflow |
-| `/harness-audit` | Score HQ setup quality across categories |
-| `/cleanup` | Audit and clean HQ to enforce current policies |
-
-### Misc
-| Command | What it does |
-|---------|--------------|
-| `/personal-interview` | Deep interview to populate profile / voice |
-| `/ascii-graphic` | Generate ASCII block-art banners for posts and OG images |
-
-## hq doctor — hook guardrail diagnostics
-
-`hq doctor` is the single command that answers whether your HQ hook guardrails
-are actually wired and firing, on whichever agent platform you are running
-(Claude Code, Codex, or Grok Build). It is read-only and fully offline — no HQ
-login, no vault access, no network — because it has to work precisely when the
-rest of the toolchain is suspect. It absorbs the older `check-hq-hooks.sh` (now a
-thin wrapper that calls `hq doctor` and degrades to an inline check when the CLI
-is absent) and the `/harness-audit` hook-coverage score.
-
-| Invocation | What it does |
-|------------|--------------|
-| `hq doctor` | Wiring checks: every hook registration across Claude/Codex/Grok is present, executable, correctly gated, and not word-split; plus the runtime probe (did hooks actually fire this session). Never executes a hook. |
-| `hq doctor --deep-test` | Everything above, then actually fires your blocking hooks with crafted inputs through the real `hook-gate.sh` under all three profiles — in a throwaway sandbox, never your live tree — to prove they block what they claim to. |
-| `hq doctor --fix` | Applies only the allowlisted safe repairs (restore an executable bit, add a hook id to gate profiles it is missing from, re-register an on-disk hook) behind a backup, a diff preview, interactive confirmation, and a dirty-tree refusal. Never rewrites a hook's body or deletes a file. |
-| `hq doctor --json` | Emits the machine-readable, versioned document (schema version, detected platform, resolved root, and every result). This is what `/harness-audit` and CI consume. |
-| `hq doctor --session-id <id>` | Scopes the runtime probe's ledger check to that exact session, so an older session's ledger cannot be mistaken for the current runtime (useful on app/SDK hosts). |
-
-**Exit code:** `0` unless some result is `FAIL` or `UNKNOWN`; `1` when any is.
-`WARN`, `UNTESTED`, `NA`, and `KNOWN-DEFECT` are reported but never fail the
-command — a doctor that goes red on a healthy install would train you to ignore
-it, which is the exact failure mode it exists to prevent.
-
-**Status vocabulary** (the load-bearing part — these never collapse into `PASS`):
-
-| Status | Meaning |
-|--------|---------|
-| `PASS` | Verified correct. |
-| `FAIL` | Verified broken — fix it. |
-| `WARN` | Non-blocking concern worth a look (e.g. an orphaned hook, a stale allowed-divergence entry). |
-| `UNTESTED` | Wired but never exercised: the hook is registered but has no fixture, so its behaviour has not been proven. Coverage is reported as a `tested/total` line so this stays visible. |
-| `NA` | Untestable on this platform (e.g. a Grok passive-event hook that cannot inject model-facing context). Not a pass and not a failure — the platform simply cannot run the check. |
-| `UNKNOWN` | Could not be determined — the host platform was unidentifiable, or a check could not run. Fails the command rather than claiming a verdict it cannot support. |
-| `KNOWN-DEFECT` | A tracked, unfixed defect pinned by an `expectedFailure` fixture marker. Always printed and counted separately, but never fails the command; if it starts passing, the doctor warns that the marker is stale. |
-
-The distinction between `UNTESTED` / `NA` / `UNKNOWN` and `PASS` is the design's
-central safeguard: a false `PASS` is worse than no tool, because it retires the
-instinct to check by hand.
-
-## Workers
-
-```
-/run                                   # see all
-/run frontend-designer
-/run frontend-designer build
-/run content-brand "tone analysis"
-```
-
-**Standalone public workers** (`core/workers/public/`):
-
-| Worker | Purpose |
-|--------|---------|
-| frontend-designer | UI generation |
-| qa-tester | Automated website testing (Playwright) |
-| security-scanner | Security scanning |
-| pretty-mermaid | Mermaid diagram generation |
-| site-builder | Static site generation |
-| knowledge-tagger | Knowledge classification |
-| exec-summary | Executive summary generation |
-| accessibility-auditor | Accessibility checks |
-| performance-benchmarker | Performance analysis |
-| ascii-artist | ASCII block-art generation |
-| paper-designer | Document / paper layout |
-
-**Dev Team (18)** — `core/workers/public/dev-team/`:
-project-manager, task-executor, architect, backend-dev, database-dev, frontend-dev, infra-dev, motion-designer, code-reviewer, knowledge-curator, product-planner, qa-tester, reality-checker, context-manager, codex-engine, codex-coder, codex-reviewer, codex-debugger
-(Gemini CLI workers gemini-coder / gemini-reviewer install via the optional `@indigoai-us/hq-pack-gemini` pack.)
-
-**Content Team (5)** — `core/workers/public/content-*/`:
-content-brand, content-sales, content-product, content-legal, content-shared (library)
-
-**Social Team (5)** — `core/workers/public/social-*/`:
-social-shared (library), social-strategist, social-reviewer, social-publisher, social-verifier
-
-**Gardener Team (3)** — `core/workers/public/gardener-team/`:
-garden-scout, garden-auditor, garden-curator
-
-**Company Workers** (`companies/{co}/workers/`):
-
-Each company can scaffold its own private workers via `/newworker`. They live under `companies/{co}/workers/` and stay isolated from other companies. Use `/run {worker-id} {skill}` to invoke them.
-
-## Companies
-
-Each company owns its settings, data, and knowledge.
-
-```
-companies/
-├── _template/      # Skeleton copied when scaffolding a new company
-├── manifest.yaml   # Company registry
-└── {company}/      # Add one directory per company you manage (via /newcompany)
-```
-
-A scaffolded company contains:
-
-```
-companies/{co}/
-├── data/           # Exports, reports, journal entries
-├── hooks/          # Company-scoped hooks
-├── knowledge/      # Company knowledge base (embedded git repo)
-├── people/         # Contact / personnel records
-├── policies/       # Company-scoped rules
-├── projects/       # PRDs and project state
-├── repos/          # Symlinks → repos/{public|private}/
-├── settings/       # Credentials & config
-├── skills/         # Company-scoped skills
-├── workers/        # Company-scoped workers
-└── workspace/      # Company-scoped scratch / drafts
-```
-
-## Projects
-
-PRDs live at `companies/{co}/projects/{name}/prd.json` for company work, or `personal/projects/{name}/prd.json` for personal/HQ work, with `README.md` as the human-readable view.
-
-```
-/plan "Build dashboard"          # creates PRD
-/run-project customer-cube      # execute via Ralph loop / Codex
-```
-
-## Directory Structure
-
-```
-HQ/
-├── AGENTS.md                  # Charter for Claude / Codex sessions
-├── .claude/
-│   ├── CLAUDE.md
-│   ├── commands/              # Slash commands (53)
-│   ├── hooks/                 # Lifecycle hooks (32)
-│   ├── skills/                # Skill definitions (55)
-│   ├── output-styles/
-│   ├── scripts/
-│   └── settings.json / settings.local.json
-├── core/
-│   ├── core.yaml              # Core manifest
-│   ├── docs/hq/               # README, CHANGELOG, MIGRATION, USER-GUIDE
-│   ├── knowledge/
-│   │   ├── public/            # Bundled public knowledge bases
-│   │   └── private/           # Private knowledge bases (populated via packs / sync)
-│   ├── packages/              # Packaged extensions
-│   ├── policies/              # Cross-cutting rules (~259)
-│   ├── scripts/               # Shared shell utilities
-│   ├── settings/              # Orchestrator config
-│   └── workers/
-│       ├── public/            # Bundled workers (dev-team, content-*, social-*, gardener-team, …)
-│       └── registry.yaml
-├── companies/
-│   ├── _template/             # Skeleton for new companies
-│   ├── manifest.yaml
-│   └── {co}/                  # One directory per company
-├── personal/
-│   ├── agents-profile.md
-│   ├── agents-companies.md
-│   ├── knowledge/
-│   ├── projects/              # Personal/HQ project scratch
-│   ├── policies/
-│   ├── settings/
-│   ├── skills/
-│   └── workers/
-├── repos/
-│   ├── public/                # Open-source repos
-│   └── private/               # Private repos
-└── workspace/
-    ├── baseline/              # Reference baselines
-    ├── checkpoints/           # Session saves
-    ├── drafts/                # In-flight drafts
-    ├── learnings/             # Captured learnings
-    ├── orchestrator/          # Ralph loop workflow state
-    ├── reports/               # Generated reports
-    ├── scratch/               # Free-form scratch
-    └── threads/               # Session threads + handoff.json
-```
-
-## Plans and limits
-
-HQ has three plans: **Starter**, **HQ Workforce** ($500/month per workspace), and
-**Enterprise**.
-
-Starter is free. It holds up to 5 members and includes 1 integration. MCP,
-Atlas, and telemetry are not included. Everything else — knowledge, projects,
-policies, workers, secrets, vault storage, `hq deploy`, and `hq share` — works
-the same as on the paid plans.
-
-### When a workspace goes over
-
-A Starter workspace locks as soon as it goes over 5 members. There is no grace
-period and no countdown.
-
-A locked workspace is read-only. Nothing is deleted or hidden, and everyone can
-still read everything. Writes are refused until the workspace is back inside the
-limits.
-
-There are two ways out, and only the workspace owner can do either:
-
-1. Remove members until there are 5 or fewer. Removing someone from a workspace
-   does not delete their personal HQ or the work they saved into the workspace.
-2. Upgrade to HQ Workforce at $500/month from the workspace billing page.
-
-Either one unlocks the workspace right away.
-
-Existing integration connections on a locked Starter workspace are disabled, not
-deleted. Upgrading turns them back on without reconnecting anything.
-
-### What you'll see
-
-The owner gets one email when the workspace locks, a reminder at most once every
-7 days while it stays locked, and one confirmation when it unlocks. Billing mail
-comes from billing@hqforwork.com, and billing links go to hq.computer, which is
-the console.
-
-In the console you'll see a lock banner, an upgrade wall, and a team roster that
-counts members against the limit. In a Claude Code session, `/startwork` shows a
-short notice on every turn while the workspace is over its limits.
-
-## Meeting notes, signals & ontology
-
-HQ captures these **natively, per company** — check HQ first, not your email or a third-party notetaker.
-
-- **Meeting notes** — recordings/transcripts the HQ meeting bot ingests into `companies/{co}/sources/meetings/`. Read them with `/meeting-notes` (or `hq meetings list|notes --company {co}`).
-- **Signals** — decisions, action items, wins, risks, open questions, and commitments extracted from your meetings, in `companies/{co}/signals/`. Read them with `/signals`.
-- **Ontology** — situational context about a company (who/what is active, recent decisions) via the `ontology` skill.
-
-**Turnkey setup (activation ladder):**
-
-1. Make the company cloud-backed → `/designate-team {co}`.
-2. Invite the HQ meeting bot to a call → notes ingest into `companies/{co}/sources/meetings/` automatically.
-3. Signals are extracted from ingested notes into `companies/{co}/signals/`; ontology context follows.
-
-**Your preference for "meeting notes":** defaults to HQ-native. To point a company at email instead, set `meeting_notes_source: email` in `companies/{co}/settings/knowledge/preferences.yaml` (global default lives in `personal/settings/knowledge-preferences.yaml`).
-
-> Signals extraction and the ontology gardener run on HQ cloud and are part of HQ Workforce ($500/mo) and Enterprise. They are not included in the free Starter plan. Cloud-back a company with `/designate-team` to turn them on. Reference: `core/knowledge/public/hq-core/native-knowledge-stores.md`.
-
-## Typical Session
-
-1. `/startwork` — pick company/project/repo, gather context
-2. Do work
-3. `/checkpoint` — save progress
-4. `/handoff` — prep for next session
-
-## Knowledge Bases
-
-**Public** (in `core/knowledge/public/`):
-- `Ralph/` — coding methodology
-- `agent-browser/` — browser automation patterns
-- `ai-security-framework/` — security practices
-- `dev-team/` — dev team patterns
-- `getting-started/` — onboarding material
-- `hq-core/` — thread schema, HQ patterns
-- `loom/` — Loom agent patterns (reference)
-- `projects/` — project templates
-- `workers/` — worker framework reference
-
-**Private** (in `core/knowledge/private/`):
-- Empty by default — populated via packs (e.g. `@indigoai-us/hq-pack-*`) or sync.
-
-**Company-level** (in `companies/{co}/knowledge/`):
-- Each company has an embedded git repo populated through use.