estack-drive-cli-agent: persist Windows sandboxed GitHub-auth guidance in source

[ElliotDrel]

Feedback

The installed ~/.agents/skills/estack-drive-cli-agent copy must not be edited directly. Improvements need to be recorded in the E-Stack source workflow so they survive reinstall/update.

Context

On Windows, a delegated codex exec --sandbox workspace-write run uses the restricted sandbox identity and cannot read the host Windows Credential Manager. gh can therefore report an invalid token even when host-side gh auth status and gh api user succeed for the signed-in account.

--approve-for-me only changes approval handling inside the sandbox; it does not give the delegated run host-keyring access. danger-full-access and --yolo should not be prescribed as an authentication workaround.

Requested skill guidance

Document a durable pattern for delegated work:

1. Set sandbox, approval, and working directory explicitly per codex exec invocation.
2. Keep delegated coding work sandboxed (read-only or workspace-write).
3. Perform authenticated GitHub reads and mutations in the parent host session or a connected GitHub integration, before or after delegation.
4. Have the delegated agent return the exact GitHub action needed rather than running gh itself.
5. Treat updates to the installed skill copy as feedback for the E-Stack source, not as a persistent fix.