@indigoai-us/hq-cli 5.288.0 → 5.290.0

package/CHANGELOG.md

@@ -2,21 +2,43 @@
 
 ## [Unreleased]
 
+## [5.290.0] — 2026-09-29
+- A failed `hq update` restores the previous working hq-cli install when it could be backed up, instead of leaving the CLI partially updated.
+
 ## [5.288.0] — 2026-09-29
 
+### Added
+
+- `hq core ontology merge-copies --rewrite-refs` (flag `checkpoint.ontology.merge-rewrite-refs`, default off) re-points signal refs, invoice and bill links, source and knowledge links from a merged copy to its survivor and carries the copy's external ids and web domains; a pair whose files hold different values for one external id stays held (`external_id_conflict`).
+- A `--only` entry can carry `resolve_external_ids: { <provider>: { primary, namespace, object_type? } }`. With `--rewrite-refs`, a conflicting provider id then keeps `primary` in `external_ids` and moves the pair's other id to the survivor's `external_refs` (`system`, `namespace`, `objectType`, `recordId`), so no id is dropped. A `primary` that matches neither id still holds the pair.
+
+### Fixed
+
+- `hq core ontology merge-copies --variants` no longer counts a copy's own `# Name` heading as unmerged text, so a merged variant copy can be deleted.
+- `merge-copies` no longer moves a copy's links to itself or to its original into the original, and does not count them or the `## Relationships` heading as unmerged text.
+- `merge-copies` now finds signal `entity_refs` written with a `.md` suffix, so it holds (or, with `--rewrite-refs`, re-points) them instead of deleting a copy they still name.
+- `merge-copies --rewrite-refs` no longer holds a survivor as `merge_invalid` when it gains external ids but has no `web_domains` key (or the reverse).
+- `merge-copies` treats an annotation list item whose first key is `path:` as a link to the copy, so it no longer deletes a copy such an annotation still names.
+
 ## [5.287.0] — 2026-09-29
 - Group hook-timeout events by script while preserving triage diagnostics.
 - Preserve safe slow-child script basenames in hook-timeout diagnostics.
 - Cloud provisioning and retirement now stop after 15 seconds when a Vault API request stalls, with a clear timeout error.
+- In the HQ desktop app, clicking "Explain HQ first" in the setup bot now shows the fixed explanation of HQ at once, with no model turn. The setup worker ships that text in `skills/explain-hq.md`, and the bot reads the same file when someone asks in their own words.
 - Add native TypeScript implementations for four `hq core` worktree and
   handoff scripts behind the default-off `core-native-handoff` flag. The
   original shell assets remain bundled as the rollback path.
+- Add default-off native `hq core handoff finalize`, `post`, and `open-steps` commands with the staging scripts retained as the rollback path.
 
 ### Fixed
 
 - `hq team-sync` keeps its successful no-team result, reports which company
   directories are cloud-backed, and points to `hq sync pull --all` and
   `hq sync status` for cloud-backed companies.
+- An unconfirmed Outpost pickup acknowledgement keeps its mirror queued with
+  `outcome_unknown` and its command id. Reconcile uses a strict owner snapshot;
+  it marks the mirror `remote_lost` only after the 15-minute grace when the
+  owner confirms the lane is missing. Unreachable owners remain counted.
 
 ### Fixed
 

package/assets/bot-workers/setup/skills/explain-hq.md

@@ -0,0 +1,35 @@
+---
+name: explain-hq
+description: The fixed explanation of HQ, sent when the person asks for it at the start of setup. It is sent word for word, by you or by the HQ app.
+---
+
+# Explaining HQ at the start
+
+This is the one explanation of HQ that setup gives. It is sent word for word
+and never reworded, shortened or added to.
+
+- **When you send it** (they asked for the explanation in their own words, or
+  they clicked "Explain HQ first" and your turn does not start with a note
+  from the HQ app saying it already went out): send the text under "The
+  explanation" as written. Then, in the same message, one line saying you are
+  starting, and the first unfinished step's one question.
+- **When the HQ app sends it** (they clicked "Explain HQ first"): the app
+  sends the text under "The explanation" at once, followed by the text under
+  "After the explanation, when the app sends it". Your next turn starts with
+  a note saying so. Do not send the explanation again.
+
+## The explanation
+
+**One shared brain for your company's AI.** Your clients, decisions, meeting notes, connected apps, keys and skills live in one place, and every AI that works for you reads from it and adds to it.
+
+**It works with the agents you already use.** Claude Code, Codex or Cursor, opened in your HQ folder, already know your business. You can put agents in Slack so your team can ask them things where they already talk, and connect other agents from the HQ console under Agents. Messaging bots in this app is one more way in, not the main one.
+
+**It's built for your team.** Invite someone and their AI knows the business on day one. Connected apps and keys can be shared with them without passing passwords around, and each company stays separate.
+
+## After the explanation, when the app sends it
+
+Ready to start the setup?
+
+```hq-block
+{"v":1,"blocks":[{"kind":"suggestions","items":["Let's start","How is this different from Claude?"]}]}
+```

package/assets/bot-workers/setup/worker.yaml

@@ -42,6 +42,9 @@ skills:
   - name: standing-help
     description: "How to behave once setup is finished: the always-there helper who does the thing rather than describing it."
     doc: skills/standing-help.md
+  - name: explain-hq
+    description: "The fixed explanation of HQ for someone who asks for it at the start of setup. Sent word for word, by you or by the HQ app."
+    doc: skills/explain-hq.md
 
 instructions: |
   # Setup
@@ -256,28 +259,26 @@ instructions: |
 
   ## Explaining HQ at the start
 
-  When they answer the first question by asking for the explanation, give it
-  in three short paragraphs, in this order, each one opening with a short
-  bold lead (the only bold in the message), in your own words but keeping
-  every point:
-
-  1. **One shared brain for your company's AI.** Their clients, decisions,
-     meeting notes, connected apps, keys and skills live in one place, and
-     every AI that works for them reads from it and adds to it.
-  2. **It works with the agents you already use.** Claude Code, Codex or
-     Cursor opened in their HQ folder already know their business. They can
-     put agents in Slack so their team can ask them things where they already
-     talk, and connect other agents from the HQ console under Agents.
-     Messaging bots in this app is one more way in, not the main one.
-  3. **It's built for your team.** Invite someone and their AI knows the
-     business on day one. Connected apps and keys can be shared with them
-     without passing passwords around, and each company stays separate.
-
-  Then one line that you are starting, and the first unfinished step's one
-  question, in the same message. Do not ask whether the explanation made
-  sense, and do not offer a tour. If they ask how to do one of those things
-  (a Slack agent, an outside agent, inviting someone, sharing an app or a
-  key), walk them through it using `skills/agents-and-team.md`.
+  The explanation is fixed, and it lives in `skills/explain-hq.md`. The same
+  text goes out whether you send it or the HQ app does, so never write your
+  own version.
+
+  When they click "Explain HQ first", the HQ app sends the explanation for
+  you straight away, and your next turn starts with a note from the app
+  saying it went out. The question is then answered: write `Intro: explained`
+  in your progress note, do not explain HQ again, and carry on with the first
+  unfinished step's one question.
+
+  When they ask for the explanation any other way (in their own words, or by
+  clicking "Explain HQ first" with no note from the app at the start of your
+  turn), read `skills/explain-hq.md` and send the text under its "The
+  explanation" heading word for word. Then one line that you are starting,
+  and the first unfinished step's one question, in the same message.
+
+  Do not ask whether the explanation made sense, and do not offer a tour. If
+  they ask how to do one of those things (a Slack agent, an outside agent,
+  inviting someone, sharing an app or a key), walk them through it using
+  `skills/agents-and-team.md`.
 
   ## How you make them feel it
 
@@ -407,7 +408,8 @@ instructions: |
     company", "Just for me". Put the answer you would recommend first.
   - **You offered a choice or a yes/no:** "Want me to invite them now?" gets
     "Yes, invite them", "Not yet".
-  - **The explain-or-jump question:** "Explain HQ first", "Jump straight in".
+  - **The explain-or-jump question:** "Explain HQ first", "Jump straight in",
+    in exactly those words. The HQ app answers "Explain HQ first" by itself.
   - **You finished something and did not ask anything:** the one or two next
     steps most people would take ("Connect my calls", "How do I add my team?").