Validate install:local from a scratch clone (fresh machine) #89

New issue

Closed

opened 2026-08-27 23:59:07 +00:00 by david · 1 comment

david commented

2026-08-27 23:59:07 +00:00

Owner

Summary

Clone the repo fresh to /tmp and run npm run install:local there, verifying the same checks as the dev machine from a clean clone — simulating a fresh machine.

Background

Proves the flow works from any git checkout, not just the dev machine. Part of the npm run install:local feature (tracking issue #41).

Depends on: #92 (Validate install:local end-to-end on the dev machine).

Implementation Details

git clone https://git.excelera.net/david/pi-extensions-and-skills /tmp/pesk-test && cd /tmp/pesk-test && npm run install:local
Then verify:
- exit code 0
- pi list shows a local-path entry; no URL entry for this repo remains
- /reload + /skills = 12 skills
- spot-check the extension tools (note: environment-dependent checks — e.g. postgres against a DATABASE_URL, forgejo token — may not apply on a scratch machine; verify what can be verified and record the limitations explicitly)
Record every result where the plan says to record it.

Acceptance Criteria

Clone + npm run install:local exits 0 in the scratch clone.
pi list shows a local-path entry; no URL entry for this repo remains.
/reload succeeds; /skills lists 12 skills.
Extension spot-checks pass where the environment allows; environment-limited checks are noted explicitly in the recorded results.

Test Plan

Run the commands in the plan's validation section (§5.2) and record each result.

## Summary Clone the repo fresh to `/tmp` and run `npm run install:local` there, verifying the same checks as the dev machine from a clean clone — simulating a fresh machine. ## Background Proves the flow works from any git checkout, not just the dev machine. Part of the `npm run install:local` feature (tracking issue #41). **Depends on:** #92 (Validate install:local end-to-end on the dev machine). ## Implementation Details - `git clone https://git.excelera.net/david/pi-extensions-and-skills /tmp/pesk-test && cd /tmp/pesk-test && npm run install:local` - Then verify: - exit code 0 - `pi list` shows a local-path entry; no URL entry for this repo remains - `/reload` + `/skills` = 12 skills - spot-check the extension tools (note: environment-dependent checks — e.g. postgres against a `DATABASE_URL`, forgejo token — may not apply on a scratch machine; verify what can be verified and record the limitations explicitly) - Record every result where the plan says to record it. ## Acceptance Criteria - [ ] Clone + `npm run install:local` exits 0 in the scratch clone. - [ ] `pi list` shows a local-path entry; no URL entry for this repo remains. - [ ] `/reload` succeeds; `/skills` lists 12 skills. - [ ] Extension spot-checks pass where the environment allows; environment-limited checks are noted explicitly in the recorded results. ## Test Plan - Run the commands in the plan's validation section (§5.2) and record each result.

david added this to the M5 - Validation milestone

2026-08-27 23:59:07 +00:00

david added the

feature

label

2026-08-27 23:59:07 +00:00

david referenced this issue

2026-08-28 01:25:10 +00:00

issue-89: Validate install:local from a scratch clone (fresh machine) #97

david closed this issue

2026-08-28 01:25:12 +00:00

david commented