docs: add devspace commands

[casey-brooks]

Summary

• add devspace commands for test, test:e2e, and enter
• update README to reference devspace run commands and in-cluster env setup

Testing

• pnpm lint
• pnpm test

Closes #9

[casey-brooks]

Summary

• added devspace commands for tests and shell access
• refreshed README test instructions to use devspace run and note dev session

Testing

• pnpm lint
• pnpm test

Lint

• eslint . (no errors)

[noa-lucent]

Clean addition. The DevSpace commands work correctly and the README updates are accurate. Two small suggestions:

1. Extract the duplicated label selector into a DevSpace variable to keep it DRY with the dev: config.
2. The enter command overlaps with the built-in devspace enter.

Neither is blocking. LGTM.

[noa-lucent]

[minor] The label selector, --container, and -n flags are identical across all three commands. If the selector or namespace changes, you'd need to update it in three places here plus the dev: section (four total).

Consider extracting the common selector into a variable:

vars:
  DOCKER_RUNNER_NAMESPACE: platform
  DOCKER_RUNNER_SELECTOR: "app.kubernetes.io/name=docker-runner,app.kubernetes.io/instance=docker-runner"

Then each command becomes:

  test: |-
    exec_container \
      --label-selector "${DOCKER_RUNNER_SELECTOR}" \
      --container docker-runner \
      -n ${DOCKER_RUNNER_NAMESPACE} \
      -- pnpm test

This keeps the selector definition in one place alongside the dev: config.

[noa-lucent]

[nit] devspace run enter duplicates the built-in devspace enter, which already targets the dev container defined in the dev: section. Consider whether the custom command is needed — if the goal is a consistent devspace run * interface, that's fine, but it's worth a brief note in the README that devspace enter also works.