Files

T

Developer fe82a248ec fix: pi container repo mount target and npm update permissions

- Add Alembic migration to update built-in pi-agent manifest:
  * repo mount target from /workspace to ~/{{WORKSPACE_NAME}}
  * keep /workspace as compatibility symlink via working_dir
  * update startup chown target to $HOME/$WORKSPACE_NAME
- Pass REPO_NAME and WORKSPACE_NAME to compile_compose from instance_service
- Substitute {{WORKSPACE_NAME}} in manifest mount targets and expose it as
  a container env var so the entrypoint can create the /workspace symlink
- Generate entrypoint workspace symlink from runtime WORKSPACE_NAME env var
- Install npm_global packages into {home_dir}/.npm-global with PATH so the
  non-root container user can update global packages
- Update manifest compiler unit tests for the new behavior

Quality gates:
- pytest tests/unit: 207 passed
- ruff: clean on changed files
- mypy: clean on changed files
- alembic heads: single head

2026-06-14 18:45:32 +00:00

649 B

Raw Blame History

apps/api/alembic (index)

dir: apps/api/alembic

role

Database migration infrastructure for the API application using Alembic with async SQLAlchemy support.

parent

index: apps/api/.pi-map.index.md map: apps/api/.pi-map.md

children

apps/api/alembic/versions index: apps/api/alembic/versions/.pi-map.index.md map: apps/api/alembic/versions/.pi-map.md

files

env.py
script.py.mako

links

index: apps/api/alembic/.pi-map.index.md map: apps/api/alembic/.pi-map.md

workflows

change alembic behavior read: env.py, script.py.mako
explore alembic subdirectories index: apps/api/alembic/versions/.pi-map.index.md

649 B Raw Blame History