pi install npm:bigpowers` never provisions `scripts/` into projects — expected, or did I miss a step for pi users?

[jbalatero]

Summary

I installed bigpowers via pi install npm:bigpowers (pi.dev's package mechanism). Every lifecycle skill I run in a consumer project heads up that scripts/*.sh files don't exist there. Before filing this as a bug I want to confirm: for
the pi installation path specifically, is a project-local scripts/ supposed to exist — and if so, how is it provisioned?

What pi actually did (verified on my machine, v2.87.5):

• Installed the package to ~/.pi/agent/npm/node_modules/bigpowers/ — including its full scripts/ tree (105 scripts, e.g. run-skill-verify.sh, run-verification-gates.sh).
• Registered the package's resources. Its manifest (package.json → pi key) declares only skills + prompts:

  "pi": { "skills": ["./.pi/skills"], "prompts": ["./.pi/prompts"] }                                                                                                                                                                                

                                                                                                                                                                                                                                                      
  — no scripts, and there is no postinstall hook.                                                                                                                                                                                                     
- pi's package contract (per pi's docs, packages.md: "Pi packages bundle extensions, skills, prompt templates, and themes") has no resource type for arbitrary project files — so pi install can't provision a scripts/ dir into a consumer project,  
  even in principle.                                                                                                                                                                                                                                  
                                                                                                                                                                                                                                                      
Meanwhile the skills call bash scripts/... project-relative (e.g. fix-bug/SKILL.md:67 → → verify: test -d specs/bugs && test -f scripts/run-skill-verify.sh), so the scripts sitting inside ~/.pi/agent/npm/node_modules/bigpowers/scripts/ are       
unreachable from any project.                                                                                                                                                                                                                         
                                                                                                                                                                                                                                                      
### Reproduction                                                                                                                                                                                                                                      
                                                                                                                                                                                                                                                      
```bash                                                                                                                                                                                                                                               
  pi install npm:bigpowers     # my actual install step                                                                                                                                                                                               
  cd <any consumer project>    # no bigpowers checkout inside it                                                                                                                                                                                      
  # ask the agent to run fix-bug (or verify-work, plan-work, survey-context, …)                                                                                                                                                                       

Observed: skill's verify/HARD GATE probes scripts/X.sh → No such file or directory → agent heads up and either skips the gate or hand-vendors the script from the npm package.