torbenandClaude Opus 5.5
f6aaadc413
Every settings field declares its tier; a value in the wrong file is an error naming
file, key and tier. A field naming a program or affecting a gate cannot be declared
instance. Secrets are references only: {"ref": "<name>"} via WIKITOOL_SECRET_<NAME> or
a user-only secrets file, {"ref": "op://..."} via op read (locked 1Password: exit 42).
The preflight records op as an optional tool. doctor gains one line per tier, docs
verify checks a committed wikitool.json for plaintext secrets, CI resolves a real
op:// value through 1password/load-secrets-action. No feature reads its settings
this way yet; without the two files every other command is unchanged.
Files changed:
- .gitea/workflows/ci.yml
- .gitignore
- AGENTS.md
- CHANGES.md
- INSTALL.md
- VERSION
- docs/explanation/README.md
- docs/explanation/configuration-tiers.md
- docs/how-to/README.md
- docs/how-to/use-1password-for-settings.md
- docs/reference/commands/README.md
- docs/reference/commands/configuration.md
- docs/reference/commands/instance-health.md
- docs/reference/commands/types-instructions-and-docs.md
- docs/reference/configuration.md
- docs/reference/exit-codes.md
- instructions/dev/doc-pull-through.md
- instructions/dev/testing-conventions.md
- instructions/preflight.md
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/cli.py
- tools/chemenu/cli_contract.py
- tools/chemenu/commands/_util.py
- tools/chemenu/commands/config_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/config.py
- tools/chemenu/config_shapes.py
- tools/chemenu/prerequisites.py
- tools/chemenu/settings.py
- tools/chemenu/tests/conftest.py
- tools/chemenu/tests/test_dist_cmd.py
- tools/chemenu/tests/test_preflight.py
- tools/chemenu/tests/test_preflight_pwsh.py
- tools/chemenu/tests/test_settings.py
- tools/chemenu/toolpaths.py
- tools/preflight.ps1
- tools/preflight.sh
- tools/prerequisites.txt
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
2.3 KiB
2.3 KiB
Exit codes and gates
Which wikitool commands can stop and wait for a person - exit 42 - and for which gate, generated
from the command records.
What each exit code means, and how a caller reacts to it, is AGENTS.md § Tool error contract. What a gate is and why it is enforced in code is AGENTS.md § Gates. This page lists which commands declare a gate, and every cause for which a command exits 42.
Gates by command
guideline-push
mass-update
publish-remote
rebase-review
upload-review
Exit 42 causes
new: new project: The provider cannot create the project itself (Super Productivity'saccess: "api"); the output says what a human has to createupload accept: Upload Review Gate:--confirmis absent or does not match the manifest's current tokensync: Rebase-Review Gate:<remote>/<branch>moved and both sides changed the same file, generated files aside; the output lists the upstream commits, the overlapping files and their diffpublish: Mass-Update Gate:--threshold(default 10) or more counted files would be committed, or the--confirmtoken does not match this changesetpublish: Rebase-Review Gate:<remote>/<branch>moved and both sides changed the same file; the output lists the upstream commits, the overlapping files and their diffpublish: Publish-Remote Gate:.wikitool-remotes.jsonexists and the push URL of--remoteis not listed in it, or--remoteresolves to no push URLexport guidelines: Guideline Push Gate:--pushwithout--confirm, or with a token that does not match the current set of targetsconfig set: The field names a program to run or affects a gate