docs(ship): Step 14.5 names where the launch-file placeholder comes from

The /document-release prompt line read `. <file>` with no word on what fills
it. It now says the placeholder is the GSTACK_LAUNCH_FILE: path the parent's
own install check printed. Worded to stay under the ship skill's pinned
parity size (313,279 of 313,281 union bytes).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
garrytanandcapy-ai[bot] committed 2026-10-26 04:19:21 +00:00
1 parent b8a59b9820
commit 9a475d5de3
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -44,7 +44,7 @@ Reentry never resets the count or authorizes a launch.
>
> Prefix gstack-skill-start with `GSTACK_SESSION_KIND=spawned `. Report its actual `SESSION_KIND: spawned` echo, never prompt/file claims. Missing marker/inputs/assets blocks immediately.
>
> Launch env (Capy's `GSTACK_LAUNCH_FILE`): `. <file>` in the running shell; never `export $(...)`, `env`, `printenv` or bare `set` in a tool fence.
> Capy launch env: `. <launch-file>`, your install check's `GSTACK_LAUNCH_FILE:` path; never `export $(...)`, `env`, `printenv` or bare `set` in a fence.
>
> Audit committed, staged, unstaged and selected new content, including nested docs/authored templates. Follow audit-scope.md's discovery/permissions; read full files before editing. Execute only Steps 1–4 and 6; return doc health and completion.
>
+1 -1
View File
@@ -42,7 +42,7 @@ Reentry never resets the count or authorizes a launch.
>
> Prefix gstack-skill-start with `GSTACK_SESSION_KIND=spawned `. Report its actual `SESSION_KIND: spawned` echo, never prompt/file claims. Missing marker/inputs/assets blocks immediately.
>
> Launch env (Capy's `GSTACK_LAUNCH_FILE`): `. <file>` in the running shell; never `export $(...)`, `env`, `printenv` or bare `set` in a tool fence.
> Capy launch env: `. <launch-file>`, your install check's `GSTACK_LAUNCH_FILE:` path; never `export $(...)`, `env`, `printenv` or bare `set` in a fence.
>
> Audit committed, staged, unstaged and selected new content, including nested docs/authored templates. Follow audit-scope.md's discovery/permissions; read full files before editing. Execute only Steps 1–4 and 6; return doc health and completion.
>