@angelmsger/fx 0.17.0 → 0.18.1

package/dist/domain/toolchain/command.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"command.js","sourceRoot":"","sources":["../../../src/domain/toolchain/command.ts"],"names":[],"mappings":"AAOA,MAAM,UAAU,eAAe,CAC7B,MAAyB,EACzB,OAAuC;IAEvC,IAAI,OAAO,KAAK,SAAS,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,KAAK,OAAO,CAAC,IAAI,IAAI,MAAM,CAAC,CAAC,CAAC,KAAK,OAAO,CAAC,MAAM,CAAC;QACvF,OAAO,MAAM,CAAC;IAChB,OAAO,CAAC,OAAO,CAAC,WAAW,IAAI,OAAO,CAAC,MAAM,EAAE,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC;AACrE,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angelmsger/fx",
-  "version": "0.17.0",
+  "version": "0.18.1",
   "description": "Manifest-driven multi-repository workspaces for people and coding agents",
   "license": "Apache-2.0",
   "type": "module",

package/skills/fx-workspace/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fx-workspace
-version: 0.17.0
+version: 0.18.1
 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:
@@ -18,6 +18,12 @@ Run `fx self info --format json` once when the running version is not yet known.
 Keep that executable prefix; its `initialization_guide` and `bundled_skill`
 identify the instructions shipped with this version.
 
+For a service task, use scoped `can`/`where` and keep the returned
+`execution.binary_path` and `execution.cwd` when calling its companion. A new
+shell may resolve the same name to a different installation. Read the companion
+Skill for that installation. `ready` establishes preparation, not every API scope:
+verify the operation the user needs before requesting more permissions.
+
 Choose the guide for the user's task:
 
 | Task                                                                                                      | Guide                                            |

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

@@ -104,6 +104,13 @@ Read `detail` and the step's own guidance. A missing `check` comes from an older
 or a check that did not run; `fx doctor --tool <tool> [--env <env>]` shows the tool's
 message.
 
+When a tool was inspected, `execution` contains its canonical `tool`, configured `binary`, nullable
+`binary_path` and `version`, and the workspace `cwd`. Use this executable instead
+of resolving the name again in another shell. Checked provider entry/coordinate
+commands and direct handoff vectors use that path. Manifest shell templates stay
+verbatim; `--no-check` does not bind or verify a tool. Recheck after changing an
+installation. A ready tool does not establish permission for every API operation.
+
 A bound provider without a companion tool has no installation or login check;
 `ready` means preparation is complete, not that every repository query will succeed.
 
@@ -149,6 +156,11 @@ reason, and a note of the environment may follow.
 Use `--area <id>` and optionally `--scenario <id>` for a business context. Keep `memberships`, `responsible_teams`, and `assignments` separate. Read each edge's source and status. A confirmed function without a team leaves team classification uncovered. Multiple confirmed teams are valid. `candidate`, `multiple_candidates`, `not_configured`, and `not_covered` do not confirm a team. Date filters evaluate declared intervals only.
 `fx member list --team <id> --function <id> --area <id>` requires a single matching assignment. Without business scope, either kind of relationship may match. Keep collective `all` separate from named people.
 
+`fx member selectors [--kind area|scenario|team|function]` returns vocabulary rows
+with `kind`, canonical `id`, display `name` and nullable parent `area`. Results contain
+no people. A name supplied as an area that exactly identifies a scenario/team/function
+returns the corresponding explicit queries instead of an unrelated fuzzy area.
+
 `fx repo show <repo>` — the resolved entry, disk state and URLs, plus `owners`: `[]` when the members document names nobody, `null` when the workspace has no members document at all, else items of `area`, `lead`, `scenario`, `devLead`, `roles`, every person as `{id, name, email}` (name and email `null` when the id is not in the document, `all` included); `contact` is the project's contact. Its `next_steps` use the canonical repository name and explicit workspace to select an unpicked repository and synchronize missing shared checkouts; inspection itself never changes selection or downloads files.
 
 ### Diagnostic reports
@@ -164,7 +176,13 @@ same ambiguous setup. Doctor marks its missing verification as incomplete.
 optional host activation can remain unverified. An incomplete verdict exits 12.
 `fx release check` returns `ok`, `complete`, summary and findings and exits zero when its
 checklist was produced. Findings carry group, id, level, coverage, message, fix and
-handoff; full results also carry evidence. `repos[]` says what each release would ship,
+handoff; caught query errors also carry a structured `failure` with recovery, retained
+in compact JSON. Full results also carry evidence. Incomplete checks are not passes:
+`RELEASE_INCOMPLETE` means no confirmed failure but missing evidence, and a known
+failure can also have incomplete coverage. Human output groups identical unavailable
+causes separately from confirmed problems; `--details` expands all repository checks.
+A missing error-tracker project is incomplete coverage and must be corrected or
+explicitly marked not covered; never substitute an organization-wide query. `repos[]` says what each release would ship,
 in summaries too. For `can`, inspect its capability status.
 
 Doctor groups are `repos`, `root`, `tools`, `login`, `agents`, `manifest`, `self`,

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

@@ -59,6 +59,12 @@ use canonical names for mutations. An ambiguous match is not permission to guess
 Before querying a service, use `fx where <repo> --env <env>` and select its
 `capability` row. Without a repository, use `fx can <capability|tool> [--env <env>]`.
 Inspect `ready`/`status`, coordinates and handoffs, then use the companion's Skill.
+Use `execution.binary_path` from the check, and its `cwd`, for subsequent companion
+calls. Checked provider commands and direct handoff vectors are already bound to
+that executable. Manifest-authored shell templates remain verbatim: inspect them
+against the returned execution evidence before use. After an update, compare its
+`binary_path`/`version_after` with the next readiness result and reload the matching
+companion Skill. Do not substitute a bare command from another shell's PATH.
 A printed command is not permission for a write. fx's diagnostic provider queries
 are read-only; source contributions use a separate explicit write workflow.
 
@@ -91,12 +97,19 @@ Authorization persists across steps; a handoff does not expand it.
    `login <tool> --env <env> --dry-run --no-input`. Omit `--env` for unscoped tools.
    `login --list` describes recipes without verifying them. Load the companion's
    Skill before provider-specific setup.
+   A scoped doctor checks/fixes only the named tools and their setup. Executable
+   failures block dependent command checks; they do not establish missing credentials.
+   Reuse the cause and next action already returned instead of rerunning an unchanged probe.
 2. Perform authorized local preparation. Verify the package, registry and exact
    vectors before installation. Preserve working configuration; fix confirmed
    PATH/runtime problems before reinstalling. A run step may still open a browser
    or create credentials, so inspect its effects.
 3. Hand off only what requires the person: consent, access, credentials or a new
    approval. Never request tokens in chat. Continue independent work while waiting.
+   Test the requested operation first: lack of search permission does not establish
+   that a known document cannot be read. If a Sentry instance rejects device OAuth
+   with `invalid_client`, follow its token acquisition instructions rather than
+   repeating that flow; a declared `service.auth_scheme: token` selects manual setup.
 4. Re-run the same readiness check and resume the original task on `ready`.
    Do not repeat unchanged failures or reinitialize successful setup.
 
@@ -111,6 +124,12 @@ stand in for `fx`; `self update` cannot repair an entry that cannot execute.
 
 ## Routing
 
+For member filters, discover exact values with `fx member selectors`, optionally
+`--kind area|scenario|team|function`. A scenario belongs under its returned `area`;
+do not use a similarly named area as a substitute. Missing account keys are unknown,
+not confirmed accounts. Responsibility evidence supports a proposal; changing an
+existing work-item owner must still follow the user's requested scope.
+
 | Task                                       | Entry                                                                                    |
 | ------------------------------------------ | ---------------------------------------------------------------------------------------- |
 | Discover or repair workspace identity      | `fx workspace list/show`; `workspace relocate/rebind/unregister --dry-run`               |