Merge pull request #12099 from KHG420/codex/studio-installed-scenario-guide

docs(studio): run scenario exercises from installed packages

examples/api-notes-kit/README.md

@@ -57,8 +57,8 @@ The unit tests check pointer escapes, array-index rules, missing/external
 targets, and recursive references; they also run without network access.
 
 Create a temporary output directory and select it as the task's write scope.
-Invoke `api-notes` with the installed `fixture/openapi.json` path and ask for
-`api-notes.md` there.
+Invoke `/api-notes-kit:api-notes` with the absolute path to the installed
+`fixture/openapi.json` and ask for `api-notes.md` in the output directory.
 
 Follow `skills/api-notes/references/scenario.md`; it defines
 both the minimum guide and the failure behavior. Check each generated claim

examples/frontend-page-kit/README.md

@@ -30,9 +30,19 @@ reasonix plugin doctor frontend-page-kit
 reasonix plugin show frontend-page-kit
 ```
 
-1. Copy `skills/frontend-page/fixture/` from this package to a new temporary
-   workspace. Keep the tracked inputs unchanged. The fixture intentionally
-   contains the task inputs only; the selected model creates the page there.
+Use the package root printed by `plugin show` to copy only the exercise inputs:
+
+```sh
+package_root='/absolute/path/from/plugin-show'
+workspace_root=$(mktemp -d "${TMPDIR:-/tmp}/reasonix-frontend-page.XXXXXX")
+cp "$package_root/skills/frontend-page/fixture/brief.md" \
+   "$package_root/skills/frontend-page/fixture/tickets.json" "$workspace_root/"
+cd "$workspace_root"
+```
+
+1. Keep the installed inputs unchanged and record `workspace_root` for cleanup.
+   The source checkout is not needed after copy installation. The fixture
+   contains task inputs only; the selected model creates the page there.
 2. Open a Reasonix session in that temporary workspace. Invoke
    `/frontend-page-kit:frontend-page` with the task below.
 

examples/issue-fix-kit/README.md

@@ -29,9 +29,20 @@ reasonix plugin doctor issue-fix-kit
 reasonix plugin show issue-fix-kit
 ```
 
-1. Copy `examples/issue-fix-kit/fixture/` to a new temporary directory. Keep the
-   tracked fixture unchanged so the exercise remains reproducible.
-2. In that copy, run `go test ./...` and observe the oversized-limit panic.
+Use the package root printed by `plugin show` to make a separate task workspace:
+
+```sh
+package_root='/absolute/path/from/plugin-show'
+scenario_root=$(mktemp -d "${TMPDIR:-/tmp}/reasonix-issue-fix.XXXXXX")
+cp -R "$package_root/fixture/." "$scenario_root/"
+cd "$scenario_root"
+go test ./...
+```
+
+1. Keep the installed fixture unchanged so the exercise remains reproducible.
+   Record `scenario_root` for the task and later cleanup; the source checkout is
+   not needed after copy installation.
+2. Observe the oversized-limit panic in the workspace's initial test run.
 3. Open a Reasonix session in the temporary fixture. Invoke
    `/issue-fix-kit:issue-fix` with the task below.
 
@@ -47,7 +58,8 @@ publishing it. Record the test result before and after the change.
 1. Confirm the installed package contains the skill and both files under
    `skills/issue-fix/references/`. Copy installation must retain those files.
 2. Check the fixture's tests pass after the fix and the input is unchanged.
-   Inspect the diff and compare the handoff with `references/delivery.md`.
+   Inspect the diff and compare the handoff with the installed
+   `skills/issue-fix/references/delivery.md`.
 3. If Go is missing or a check fails, retain the evidence and report the check
    as unavailable or failed. Doctor validates the package, not the task result.
 4. Remove the test package with `reasonix plugin remove issue-fix-kit --yes`.