Move harness profiles between host and Docker and stop silent draft retargeting
Native installs left Docker-era harness profiles in harnesses.json, so every authoring launch failed trying to reach a Docker service, and a retained draft bound to the old Docker server was silently projected onto the configured one. - harness: add Profile.Mode and VerifyDockerLink as the single mode/verification helpers. `harness setup --host` configures or converts a host profile and clears docker_directory; reconfiguring a Docker-linked profile re-verifies the recorded directory still owns compose.yaml and fails naming it instead of saving a link that cannot launch. Setup's summary and `harness list` (via the new List/ListView shape) report the resulting mode and, for Docker, the directory, without changing the stored Config schema. - setup-native.py: after build/install-skill it writes host (no docker_directory) profiles for the detected harnesses, defaulting to the detected OpenCode profile rather than a stale pi default, taking models from --model or the existing valid profile and never inventing one; it clears a stale Docker link and preserves unrelated keys/profiles. Detection-only: no harness install, upgrade or download. - draft: add Draft.Resolve, the shared mismatch helper, which projects a draft onto the configured server and returns a dual-URL notice. CLI validate/submit and the TUI draft browser use it so a foreign draft is never silently retargeted; the TUI pre-wraps the notice to the panel width. - Tests cover the Docker->host and host->host transitions, the missing-directory failure, installer write/migration (Python), and the CLI/TUI notice, using the real config file path in a temp dir. - Update help text, README, docs and the packaged authoring skill reference to describe host as the default and the Docker-linked case.
This commit is contained in:
+6
-3
@@ -72,8 +72,9 @@ pipelines new "release notes" "Summarize changes and notify my phone"
|
||||
pipelines new "Text summary" --template summary
|
||||
```
|
||||
|
||||
`new` opens the configured harness (Pi or OpenCode; Docker-linked by default)
|
||||
immediately when its name/request is omitted. The skill asks only for missing
|
||||
`new` opens the configured harness (Pi or OpenCode; host by default, or
|
||||
Docker-linked when a checkout is linked) immediately when its name/request is
|
||||
omitted. The skill asks only for missing
|
||||
decisions and records the chosen name in draft metadata. `edit` accepts an exact
|
||||
name or ID, with names taking precedence over numeric IDs. Both retain private
|
||||
drafts and launch the harness once with a short `@pipelines` reference and
|
||||
@@ -144,7 +145,9 @@ the existing draft, `v` for server validation, and `s` for submission confirmati
|
||||
server you are connected to. Same-server submissions preserve create-only/version
|
||||
guards. A different destination imports the draft as a new pipeline, ignoring
|
||||
the origin's version number and refusing an existing destination name; the
|
||||
confirmation shows the destination. Retained source and origin metadata stay
|
||||
confirmation shows the destination, and opening, validating or submitting a draft
|
||||
whose recorded server differs from the configured one prints a notice naming both
|
||||
URLs so it is never silently retargeted. Retained source and origin metadata stay
|
||||
unchanged. For an edit draft, CLI `submit --expected-version N` can explicitly
|
||||
approve an update against version N on the destination (or `--force` can explicitly
|
||||
skip that version check). For unnamed drafts, submission asks you to
|
||||
|
||||
Reference in New Issue
Block a user