@alessandroraffa/tangyr 7.0.1 → 9.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -11
- package/dist/index.js +1442 -1045
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -25,16 +25,16 @@ tangyr <command>
|
|
|
25
25
|
|
|
26
26
|
### Kit management
|
|
27
27
|
|
|
28
|
-
| Command | Description
|
|
29
|
-
| ---------------------------------- |
|
|
30
|
-
| `tangyr install --kit <name>` | Install a kit resolved from configured search paths (`kitSearchPaths`/`kit` in `tangyr.config.yaml`)
|
|
31
|
-
| `tangyr install --kit-path <path>` | Install a kit from an explicit kit root path
|
|
32
|
-
| `tangyr uninstall` | Remove Tangyr from the target scope
|
|
33
|
-
| `tangyr sync` | Synchronize installed kit to the latest version
|
|
34
|
-
| `tangyr verify` | Check installation integrity against the manifest
|
|
35
|
-
| `tangyr cleanup` | Remove managed artifacts; delegates to uninstall if manifest exists
|
|
36
|
-
| `tangyr assess` | Pre-installation conflict analysis
|
|
37
|
-
| `tangyr list` | Display kits discovered in configured search paths and any installed manifests
|
|
28
|
+
| Command | Description |
|
|
29
|
+
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
|
|
30
|
+
| `tangyr install --kit <name>` | Install a kit resolved from configured search paths (`kitSearchPaths`/`kit` in `tangyr.config.yaml`) |
|
|
31
|
+
| `tangyr install --kit-path <path>` | Install a kit from an explicit kit root path |
|
|
32
|
+
| `tangyr uninstall` | Remove Tangyr from the target scope |
|
|
33
|
+
| `tangyr sync` | Synchronize installed kit to the latest version |
|
|
34
|
+
| `tangyr verify` | Check installation integrity against the manifest |
|
|
35
|
+
| `tangyr cleanup` | Remove managed artifacts; delegates to uninstall if manifest exists |
|
|
36
|
+
| `tangyr assess` | Pre-installation conflict analysis: what is there, what `onConflict` will do to it, and whether install will be refused |
|
|
37
|
+
| `tangyr list` | Display kits discovered in configured search paths and any installed manifests |
|
|
38
38
|
|
|
39
39
|
### Environment
|
|
40
40
|
|
|
@@ -407,7 +407,7 @@ reaches them).
|
|
|
407
407
|
| --------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
408
408
|
| `0` | Success | The command completed with no fatal error. A `sync`/`install` whose loss report contains only `info`/`warning`-severity entries also exits `0`. |
|
|
409
409
|
| `1` | General failure | The generic, catch-all failure code for any error not mapped to a more specific code below — including a CLI usage error such as an unrecognized command, a malformed `--kit <name>@<version>` reference, or `--offline` and `--refresh` passed together; an `install` or `sync` that would put a different kit over the one this scope holds also exits here rather than installing both (see `--replace`); a corrupt or legacy-format installation manifest (`ManifestCorruptError`, `ManifestLegacyError`, `src/core/manifest.ts`) also falls through to this code, since `handleFatalError` carries no dedicated branch for either. |
|
|
410
|
-
| `2` | Conflict |
|
|
410
|
+
| `2` | Conflict | A conflict that no posture resolves. Reached when `install` finds an instructions entrypoint Tangyr did not write — `AGENTS.md`, `CLAUDE.md`, `.opencode/AGENTS.md`, `.cursor/rules/AGENTS.md`, `.github/copilot-instructions.md`, whichever file an enabled target reads — and refuses, writing nothing, under every `onConflict` posture. `INSTALL_FOREIGN_INSTRUCTIONS` goes to stderr as JSON; `assess` and `--dry-run` predict it. Move the file aside, or fold what it says into the kit, then install again. `ConflictError` (`src/core/exit.ts`) also routes here and is thrown by no current code path. |
|
|
411
411
|
| `3` | Completed with error-severity loss | An `install`/`sync` run completes but its loss report contains at least one `error`-severity entry, distinct from the generic failure code `1`. `--ignore-errors` on `install`/`sync` forces a zero exit for authors who accept the loss. |
|
|
412
412
|
| `4` | Target not detected | Reserved for a configured target tool whose runtime cannot be detected (`TargetNotDetectedError`, `src/core/exit.ts`); declared and routed the same way as exit `2`, and likewise not thrown by any current production code path. |
|
|
413
413
|
| `5` | Authentication required | The resolved credential is missing, partially configured (see the credential-precedence trap above), or rejected by the origin (`401`/`403`) — at login, at a cold fetch, or at the post-freshness-window re-check. |
|