@angelmsger/fx 0.12.0 → 0.13.0

package/skills/fx-workspace/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fx-workspace
-version: 0.12.0
+version: 0.13.0
 description: 'Use only when the user explicitly asks for the fx workspace CLI or manifest, or the current task is inside an fx-managed workspace or routed by its fx-derived AGENTS.md. Drive workspace init and sync, repository status and selection, manifest validation and editing, companion tools and login, doctor, agent Skills, repository ownership, environment coordinates and readiness through can/where, and release checks across dependencies, branches, builds and errors. Do not use for generic Sentry, OpenObserve, Jenkins, Kubernetes, logs, errors or builds outside an fx-managed workspace.'
 metadata:
   requires:
@@ -20,11 +20,11 @@ identify the instructions shipped with this version.
 
 Choose the guide for the user's task:
 
-| Task                                                                                          | Guide                                            |
-| --------------------------------------------------------------------------------------------- | ------------------------------------------------ |
-| Prepare a workspace from a manifest, or resume unfinished preparation                         | [Initialization](references/initialization.md)   |
-| Query, synchronize or maintain an existing workspace; route a service task; edit the manifest | [Workspace tasks](references/workspace-tasks.md) |
-| Interpret a particular response field or advanced recovery contract                           | [Response contracts](references/commands.md)     |
+| Task                                                                                                      | Guide                                            |
+| --------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
+| Prepare a workspace from a manifest, set up companion tools without one, or resume unfinished preparation | [Initialization](references/initialization.md)   |
+| Query, synchronize or maintain an existing workspace; route a service task; edit the manifest             | [Workspace tasks](references/workspace-tasks.md) |
+| Interpret a particular response field or advanced recovery contract                                       | [Response contracts](references/commands.md)     |
 
 For initialization, the source and target directory are sufficient. Follow the
 initialization guide and `preparation.next`; it already includes verification.

package/skills/fx-workspace/references/commands.md

@@ -281,7 +281,10 @@ plus workspace/root, the effective enabled setting, and dated observations.
 `activation: unverified` means native trust/execution has not been established;
 a matching projection alone is not readiness. An observation whose code is
 `HOOK_PHASE_UNREPORTED` names a background phase that never answered, so its
-absence of findings is unknown rather than clean; run its `command` to find out. `fx hook enable [--dry-run]`
+absence of findings is unknown rather than clean; run its `command` to find out.
+`LOGIN_UNCHECKED` likewise says every login check that did not pass was not asked or
+gave no answer in the background run's time, the incomplete coverage `fx doctor`
+reports; it asks for no sign-in. `fx hook enable [--dry-run]`
 enables this workspace and projects selected hosts. `fx hook disable [--dry-run]`
 disables it and removes owned entries. Global `hooks` / `FX_HOOKS` gates all
 workspaces; local `hooks.enabled` gates one. `agent unpick` remains global and

package/skills/fx-workspace/references/initialization.md

@@ -46,6 +46,23 @@ source was never accepted. Preserve both streams on failure. Default results
 contain the decision and recovery; use `--details` only for a specific missing
 piece of evidence, without repeating a successful write.
 
+## Companion tools without a manifest
+
+When the user wants companion tools on this machine and has no manifest, name the
+tools they asked for; `fx tool list --catalog` shows the choices. No directory is
+given, and nothing is registered:
+
+```sh
+fx init --tools "<name,...>" --dry-run --format json
+fx init --tools "<name,...>" --format json
+```
+
+Init installs the missing tools, installs their Skills and fx's own, and checks
+each sign-in. A tool not signed in is a `handoff` blocker whose `actor: user`
+action is the tool's own setup, such as `jira-cli config init`; it asks the person
+for the service and their credentials, so give it to them instead of running it.
+After they finish, run the returned `resume`, which repeats the same `--tools`.
+
 If fx is absent, install the package/source provided by the team within the
 authorized prefix. npm configuration supplies Registry routing and authentication;
 no separate FX_REGISTRY setup is needed. Verify `self info`, then use this route.