Developer
6e33e8e4e9
The pi-agent manifest still declared an explicit repo mount with
{{WORKSPACE_NAME}}, making the mount target dependent on tool config. The
instance service now synthesizes the repo mount, so the manifest no longer
needs the explicit mount.
- Add Alembic migration 2026_06_15_090500 to remove the source_type: repo
mount from the built-in pi-agent manifest
- Add _get_repository_mount_name() helper to derive the workspace directory
name from the repository remote URL (matching git clone behavior) and
fall back to the user-provided repository name
- Use the helper for WORKSPACE_NAME/REPO_NAME in manifest, legacy dockerfile,
and legacy compose template paths
- Update unit tests for the new migration and helper
Quality gates:
- pytest tests/unit: 218 passed
- ruff: clean on changed files
- mypy: clean on changed files
- alembic heads: single head
19 lines
385 B
Markdown
19 lines
385 B
Markdown
# apps
|
|
dir: apps
|
|
|
|
index: apps/.pi-map.index.md
|
|
|
|
## role
|
|
Contains the main application entry points and executable modules for the project.
|
|
## files
|
|
## arch
|
|
Typically follows a modular architecture where each subdirectory represents a separate deployable application or service, often with shared libraries extracted to common packages.
|
|
## tags
|
|
-
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|