Configure full Docker setup and confirm consequential actions
This commit is contained in:
@@ -23,9 +23,24 @@ now references that skill directly instead of preloading instructions.
|
||||
|
||||
Native generation/assistant completion parsing is regression-tested against a
|
||||
controlled HTTP server. Full live inference, permission enforcement by real model
|
||||
tool calls, cancellation during inference, optional Docker deployment, privileged
|
||||
tool calls, cancellation during inference, Docker provider authentication, privileged
|
||||
system-wide copying, and OS service-manager registration are **not tested**.
|
||||
|
||||
The full Docker installer was exercised in an isolated Compose project with real
|
||||
ntfy and Pipelines containers: image build, account/ACL/token bootstrap, Compose
|
||||
health checks, authenticated notification publishing from the Pipelines container,
|
||||
CLI status, reinstall preservation of `.env`/token, and an empty pipeline database.
|
||||
Provider-account inspection/login completion was mocked in that installer test.
|
||||
A separate real-container PTY invocation of `opencode auth login` displayed its
|
||||
searchable provider choices and was canceled without credentials. Provider login,
|
||||
model inference and phone delivery remain **not tested**.
|
||||
|
||||
Consequential-action regressions check run/retry/cancellation and CLI publication/
|
||||
draft deletion confirmation, default-No behavior, JSON stdout cleanliness, and
|
||||
`--yes` for explicit automation. The compiled CLI/TUI PTY check verified that `q`
|
||||
does not exit, `:quit` exits, canceled retry prompts create no run, and an explicit
|
||||
`y` starts a new retry with the original input/directory and pinned version.
|
||||
|
||||
Autostart regression tests exercise both service-definition formats, scoped
|
||||
environment capture, escaping, private files, refusal to overwrite unmanaged
|
||||
files/symlinks, preview without side effects, and lifecycle calls using a mock OS
|
||||
|
||||
Reference in New Issue
Block a user