add exec, run and scale, and the agent skill

The skill documents how to use myos: what to check before touching a host
stack, how a reference resolves, what the three kinds of stack mean, and where
each failure comes from. Every command it shows was run against the fixtures
before being written down, which is how exec, run and scale turned out to be
missing.

AGENTS.md covers the other side: how to change myos without breaking the
deployments that already run it.

spec/golden/expected.cli/app-run.txt

@@ -1,26 +1,2 @@
-ERROR: unknown command: run
-Usage: myos [options] <command> [stack...] [VAR=value...] [-- args...]
-
-Options:
- -C DIR work in DIR instead of the current directory
- -e ENV environment (default: local, or ENV from the config)
- -H HOSTS run on remote hosts instead (comma separated, or "all")
- -n, --dry-run print the commands instead of running them
- -v, --verbose show what myos does
- -d, --debug show every command
- -h, --help this help
-
-Commands:
- up down start stop restart recreate manage the containers of a stack
- ps logs config exec run inspect and enter them
- ls [--groups] list the stacks myos can see
- env [VAR...] show resolved variables
- doctor check the installation
- version print the myos version
-
-Stacks:
- myos up the stack of the current directory
- myos up host a group, expanded from host=... in a .env or .mk
- myos up host/fabio a single stack
- myos up postgres:9.6 a versioned stack
-[exit 2]
+docker compose -f @WD@/docker-compose.yml -f @WD@/docker-compose.local.yml -f @WD@/docker/docker-compose.yml -f @MYOS@/share/compose/networks.yml -p tester-wd-local --project-directory @WD@ run --rm app
+[exit 0]

spec/golden/expected.cli/app-scale.txt

@@ -1,26 +1,4 @@
-ERROR: unknown command: scale
-Usage: myos [options] <command> [stack...] [VAR=value...] [-- args...]
-
-Options:
- -C DIR work in DIR instead of the current directory
- -e ENV environment (default: local, or ENV from the config)
- -H HOSTS run on remote hosts instead (comma separated, or "all")
- -n, --dry-run print the commands instead of running them
- -v, --verbose show what myos does
- -d, --debug show every command
- -h, --help this help
-
-Commands:
- up down start stop restart recreate manage the containers of a stack
- ps logs config exec run inspect and enter them
- ls [--groups] list the stacks myos can see
- env [VAR...] show resolved variables
- doctor check the installation
- version print the myos version
-
-Stacks:
- myos up the stack of the current directory
- myos up host a group, expanded from host=... in a .env or .mk
- myos up host/fabio a single stack
- myos up postgres:9.6 a versioned stack
-[exit 2]
+docker network create tester-local
+docker network create testhost
+docker compose -f @WD@/docker-compose.yml -f @WD@/docker-compose.local.yml -f @WD@/docker/docker-compose.yml -f @MYOS@/share/compose/networks.yml -p tester-wd-local --project-directory @WD@ up -d --scale app=2
+[exit 0]

spec/golden/expected.cli/cmd-env-domain.txt

@@ -0,0 +1,2 @@
+DOMAIN example.test
+[exit 0]

spec/golden/expected.cli/cmd-exec-host.txt

@@ -0,0 +1,2 @@
+docker compose -f @WD@/stack/host/consul.yml -f @MYOS@/share/compose/networks.yml -p testhost --project-directory @WD@/stack/host exec consul consul members
+[exit 0]

spec/golden/expected.cli/cmd-exec-service.txt

@@ -0,0 +1,2 @@
+docker compose -f @WD@/stack/host/fabio.yml -f @MYOS@/share/compose/networks.yml -p testhost --project-directory @WD@/stack/host exec fabio sh
+[exit 0]

spec/golden/expected.cli/cmd-ls-groups.txt

@@ -0,0 +1,4 @@
+host host/consul host/fabio host/registrator
+default postgres redis
+testing drone/drone redis
+[exit 0]

spec/golden/expected.cli/cmd-ls.txt

@@ -0,0 +1,9 @@
+@WD@/stack
+ host 3 compose file(s)
+@HOME@/.local/share/myos/stack
+ User 1 compose file(s)
+ drone 2 compose file(s)
+ host 3 compose file(s)
+ postgres 3 compose file(s)
+ redis 1 compose file(s)
+[exit 0]

spec/golden/expected.cli/cmd-run-catalogue.txt

@@ -0,0 +1,2 @@
+docker compose -f @HOME@/.local/share/myos/stack/postgres/postgres.yml -f @HOME@/.local/share/myos/stack/postgres/postgres.local.yml -f @MYOS@/share/compose/networks.yml -p tester-postgres-local --project-directory @HOME@/.local/share/myos/stack/postgres run --rm postgres psql -l
+[exit 0]

spec/golden/expected.cli/cmd-scale.txt

@@ -0,0 +1,4 @@
+docker network create tester-local
+docker network create testhost
+docker compose -f @HOME@/.local/share/myos/stack/postgres/postgres.yml -f @HOME@/.local/share/myos/stack/postgres/postgres.local.yml -f @MYOS@/share/compose/networks.yml -p tester-postgres-local --project-directory @HOME@/.local/share/myos/stack/postgres up -d --scale postgres=3
+[exit 0]

spec/golden/expected.cli/host-exec.txt

@@ -1,26 +1,2 @@
-ERROR: unknown command: exec
-Usage: myos [options] <command> [stack...] [VAR=value...] [-- args...]
-
-Options:
- -C DIR work in DIR instead of the current directory
- -e ENV environment (default: local, or ENV from the config)
- -H HOSTS run on remote hosts instead (comma separated, or "all")
- -n, --dry-run print the commands instead of running them
- -v, --verbose show what myos does
- -d, --debug show every command
- -h, --help this help
-
-Commands:
- up down start stop restart recreate manage the containers of a stack
- ps logs config exec run inspect and enter them
- ls [--groups] list the stacks myos can see
- env [VAR...] show resolved variables
- doctor check the installation
- version print the myos version
-
-Stacks:
- myos up the stack of the current directory
- myos up host a group, expanded from host=... in a .env or .mk
- myos up host/fabio a single stack
- myos up postgres:9.6 a versioned stack
-[exit 2]
+docker compose -f @WD@/stack/host/consul.yml -f @MYOS@/share/compose/networks.yml -p testhost --project-directory @WD@/stack/host exec consul
+[exit 0]