Plan / Interface amendment: resolve mecatui remote endpoints decisions and add remote commands - #2053
Merged
Merged
Conversation
Record the directing human's acceptance of the three open recommendations:
the remote: block lives in ~/.config/mecatui/settings.yaml, the kind
fixture passes profile flags with logout on destroy/reset, and endpoint
names match ^[a-z][a-z0-9-]{0,62}$ with sessions and debug reserved.
Replace decision-referencing contract text with the concrete choices and
move the plan from draft to proposed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jhrozek
approved these changes
Oct 1, 2026
ChrisJBurns
approved these changes
Oct 1, 2026
The directing human asked for CLI commands that configure endpoints in the client settings file. Add Scenario 6 and its interface: mecatui remote add/list/remove/default, editing ~/.config/mecatui/settings.yaml in place under the ADR 0345 settings-mutation rules, with no network, registry, or credential side effects. Drop the matching out-of-scope row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tgrunnagle
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stage: Plan / Interface amendment to #2049 (merged as
92683cb88)./plan-orchestratestopped at its entry gate because the merged plan still had three unchecked human decisions. This PR resolves them and adds one scope item the directing human requested.Resolved decisions (directing human accepted all three recommendations)
remote:lives in the strict, client-owned~/.config/mecatui/settings.yaml, not the shared~/.config/mecatl/settings.yaml.kind-connectandkind-loginpass profile flags against the normal client root and write no settings file; destroy/reset run a best-effortmecatui logoutfirst.^[a-z][a-z0-9-]{0,62}$;sessionsanddebugreserved; exact name match wins over host interpretation.Text that pointed at "the settings-home decision" and "the endpoint-name decision" now names the concrete file and pattern.
Added:
mecatui remotecommands (new Scenario 6, AC6.1–AC6.5)The directing human asked for CLI commands to configure endpoints. The grammar below is the agent's proposal; please review it — merging approves it.
mecatui remote add NAME RESOURCE_URL [--grpc-target] [--tls-ca] [--private-issuer --discovery-ca] [--default]— same profile flags and pairing rule asconnect; relative CA paths stored absolute; CA must be a readable PEM file; duplicate name is an error.mecatui remote list— name, resource, gRPC target, discovery policy, default marker; no network, no credentials.mecatui remote remove NAME— deletes the entry, clears a matching default, does not log out (prints themecatui logoutcommand).mecatui remote default NAME/--clear.0600file /0700dir on create.The "
mecatui remote add/list/remove" out-of-scope row is removed; editing an entry in place or logging out on remove is now listed as out of scope. Definition of done item 4 now covers theremotecommands in user docs and the kind README. The kind tasks themselves still use flags.Status moves
draft→proposed; merging this PR is the approval event. ACs 1.1–5.4 and their verify lines are unchanged.Verification
check-acceptance-plan.sh docs/acceptance/mecatui-remote-endpoints.md— passed (28 ACs with verify coverage; all human decisions resolved and recorded).task docs— exit 0.Implementation has not started;
/plan-orchestratewill re-run from the merged commit.Relates to #2049
🤖 Generated with Claude Code