eric/weatherreporter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Correct profile test boundaries and fallback coverage

Browse Source
This commit is contained in:
Eric Rakestraw
2026-08-01 17:24:21 +00:00
parent 117c5336ba
commit 1250247986
6 changed files with 393 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/troubleshooting.md
View File

@@ -1,7 +1,10 @@
# Troubleshooting
Keep failed workspace artifacts in place. When a RunID is available, start
with `weatherreporter inspect metadata RUN_ID` and use the paths in its result.
Start with the command's classified error. When content-rich prompt diagnostics
are needed, enable a new run with `--llm-debug-dir` and handle the resulting
secure capture as sensitive. Current-version workspace receipts can provide
additional context when present, but are transitional state rather than a
long-term troubleshooting interface.
## Prompt inspection or credentials fail before collection
@@ -20,9 +23,10 @@ the selected profile's YAML, ID, backend or endpoint, and model. If the model
is unexpected, first check the global `promptkit.profile` selection and then
look for a same-ID definition in the configured file or directory.
The preparation and execution receipts named by run metadata retain the
selected profile ID and effective backend/model for diagnosis, but not an
endpoint or credential. See the maintained
Current-version preparation and execution receipts may retain the selected
profile ID and effective backend/model, but not an endpoint or credential.
Use them only as supplemental context after the active command error or an
explicit secure debug capture. See the maintained
[local `weather-light` profile example](../examples/weather-light-local-profile.yml).
## Local model endpoint is unavailable
@@ -36,10 +40,11 @@ does not probe endpoints or automatically use a remote profile instead.
## Preparation, capacity, or execution fails
A preparation failure occurs before provider work; an execution failure occurs
after preparation. Both leave safe provenance and metadata when reached. A
capacity error for one batch report does not retry that report or prevent later
independent reports. Inspect the preparation or execution path, correct the
profile/backend condition, and create a new run. See [operations](operations.md).
after preparation. A capacity error for one batch report does not retry that
report or prevent later independent reports. Correct the profile or backend
condition identified by the bounded command error, then create a new run.
Use explicit secure debug capture only when additional content-rich diagnostics
are necessary. See [operations](operations.md).
## Generated text fails validation