feat: Add support for publishing with arxpm publish

README.md

@@ -17,7 +17,8 @@ workspace lifecycle, Pixi integration, and user-facing workflow commands.
 - `manifest.py`: `arxproj.toml` parsing and rendering.
 - `_toml.py`: TOML parser compatibility shim (`tomllib`/`tomli`).
 - `pixi.py`: Pixi adapter and `pixi.toml` handling.
-- `project.py`: project workflows (`init`, `add`, `install`, `build`, `run`).
+- `project.py`: project workflows (`init`, `add`, `install`, `build`, `run`,
+  `pack`, `publish`).
 - `doctor.py`: health checks for environment and manifest.
 - `cli.py`: Typer command layer.
 
@@ -27,7 +28,10 @@ workspace lifecycle, Pixi integration, and user-facing workflow commands.
 - `arxpm install`
 - `arxpm add <name> [--path PATH|--git URL]`
 - `arxpm build`
+- `arxpm compile`
 - `arxpm run`
+- `arxpm pack`
+- `arxpm publish`
 - `arxpm doctor`
 
 ## Development

docs/commands.md

@@ -34,6 +34,12 @@ arxpm install
 arxpm install --directory examples
 ```
 
+Dependency entries are installed with pip inside the project pixi env:
+
+- registry: `pip install <name>`
+- path: `pip install <path>`
+- git: `pip install git+<url>`
+
 ## `arxpm build`
 
 Compile through Pixi using the configured compiler.
@@ -49,6 +55,16 @@ Current Arx invocation uses:
 arx <entry> --output-file <out_dir>/<project_name>
 ```
 
+## `arxpm compile`
+
+Compile through Pixi using the configured compiler. This is a clearer alias for
+`arxpm build` (which is kept for compatibility).
+
+```bash
+arxpm compile
+arxpm compile --directory examples
+```
+
 ## `arxpm run`
 
 Build and then run the produced artifact through Pixi.
@@ -58,7 +74,29 @@ arxpm run
 arxpm run --directory examples
 ```
 
-Build/compiler output and the application stdout/stderr are streamed directly;
+The command shows compiler and program output directly in your terminal.
+
+## `arxpm pack`
+
+Build package artifacts locally without uploading to a registry.
+
+```bash
+arxpm pack
+arxpm pack --directory examples
+```
+
+## `arxpm publish`
+
+Build and publish the current project as a Python package that bundles
+`arxproj.toml` and `*.x`/`*.arx` sources.
+
+```bash
+export TWINE_USERNAME=__token__
+export TWINE_PASSWORD=<pypi-token>
+arxpm publish
+arxpm publish --repository-url https://test.pypi.org/legacy/
+arxpm publish --dry-run
+```
 
 ## `arxpm doctor`
 

docs/getting-started.md

@@ -30,7 +30,7 @@ The report should show:
 - pixi available
 - `arxproj.toml` found
 - `pixi.toml` found
-- `python` and `clang` declared in `pixi.toml`
+- `python`, `pip`, and `clang` declared in `pixi.toml`
 
 ## Run Example
 
@@ -40,6 +40,16 @@ python -m arxpm build --directory examples
 python -m arxpm run --directory examples
 ```
 
+## Publish Package
+
+Set Twine credentials for your package index (PyPI example):
+
+```bash
+export TWINE_USERNAME=__token__
+export TWINE_PASSWORD=<pypi-token>
+python -m arxpm publish --directory examples
+```
+
 ## Local Quality Gates
 
 ```bash

docs/index.md

@@ -23,7 +23,8 @@ only for distributing `arxpm` itself.
 - `src/arxpm/manifest.py`: parse/render `arxproj.toml`.
 - `src/arxpm/_toml.py`: TOML parser compatibility shim (`tomllib`/`tomli`).
 - `src/arxpm/pixi.py`: Pixi detection and partial `pixi.toml` sync.
-- `src/arxpm/project.py`: `init`, `add`, `install`, `build`, `run`.
+- `src/arxpm/project.py`: `init`, `add`, `install`, `build`, `run`, `pack`,
+  `publish`.
 - `src/arxpm/doctor.py`: environment and manifest checks.
 - `src/arxpm/cli.py`: Typer CLI layer.
 
@@ -34,7 +35,10 @@ arxpm init --name hello-arx
 arxpm add http
 arxpm install
 arxpm build
+arxpm compile
 arxpm run
+arxpm pack
+arxpm publish
 arxpm doctor
 ```
 

docs/manifest.md

@@ -43,4 +43,6 @@ mylib = { path = "../mylib" }
 utils = { git = "https://example.com/utils.git" }
 ```
 
-Version solving and registry resolution are intentionally out of scope in v0.
+Version solving is intentionally out of scope in v0. During `arxpm install`,
+registry dependencies are installed with `pip install <name>`, path dependencies
+with `pip install <path>`, and git dependencies with `pip install git+<url>`.

docs/pixi-integration.md

@@ -6,7 +6,7 @@
 
 `arxpm` does not own all of `pixi.toml`. It only manages:
 
-- required toolchain dependencies (`python`, `clang`)
+- required toolchain dependencies (`python`, `pip`, `clang`)
 - the `tool.arxpm` section used to track managed fields
 
 Unrelated user sections such as tasks and features are preserved.

examples/arxproj.toml

@@ -8,9 +8,6 @@ entry = "src/main.x"
 out_dir = "build"
 
 [dependencies]
-http = { source = "registry" }
-mylib = { path = "../mylib" }
-utils = { git = "https://example.com/utils.git" }
 
 [toolchain]
 compiler = "arx"

examples/pixi.toml

@@ -6,4 +6,5 @@ platforms = ["linux-64", "osx-64", "win-64"]
 
 [dependencies]
 python = "*"
+pip = "*"
 clang = "*"