Adapter: name delegate_task's task field, and say where scripts come from when they are not on disk #3

Two gaps in plugins/pstack/skills/poteto-mode/references/t3-adapter.md.

1. Name the task field

delegate_task requires its brief in a field named task, but the adapter never says so. In a dry run, agents guessed prompt because the adapter's mapping table (line 34) describes the brief without naming the field.

Fix: name the field in that row, for example: "The brief goes in task; it is self-contained: goal, file pointers, ...".

2. Say where a skill's scripts come from when they are not on disk

The skills are now served from Executor (app pstack-skills-trial on executor.planasolutions.ai, which reads this repo's main). Executor returns skill files as text. It does not put scripts/ on disk or keep executable bits, so a skill that runs <pstack-root>/skills/<x>/scripts/... has nothing to run.

Fix: add a rule under "Paths". When <pstack-root>/skills/<x>/scripts/ is missing, fetch that folder from main and run it from there:

mkdir -p "${TMPDIR:-/tmp}/pstack/skills/<x>" && \
curl -sL https://codeload.github.com/Minoo7/t3-pstack/tar.gz/main \
  | tar -xz -C "${TMPDIR:-/tmp}/pstack/skills/<x>" --strip-components=5 \
    t3-pstack-main/plugins/pstack/skills/<x>/scripts

Then run bun install --frozen-lockfile where the folder has a lockfile. The tarball keeps executable bits; a raw link does not.

Tested 2026-11-12:

• show-me-your-work/scripts/log.sh from a raw link ran.
• poteto-mode/scripts from the tarball: bun install worked and bun test watch-pr passed 54/54.

Tracking main is deliberate. A fetch can pick up a merge that lands while it runs, and that risk is accepted.

Check

• bun run check and bun test tools pass.
• Rerun the dry-run scenarios: agents name task and fetch scripts before running them.