Add a `make install` target wrapping the documented uv tool install #74

New issue

Closed

opened 2026-09-13 11:01:59 +00:00 by kilo · 0 comments

kilo commented

2026-09-13 11:01:59 +00:00

Member

Problem

There is no make install target. The documented installation path (README "Installation", D-034) is uv tool install from the checkout or a built wheel, but nothing in the Makefile wraps it, so upgrading means remembering the exact uv tool install --force invocation (and that uv tool upgrade does not apply to path-installed tools).

Proposal

Add an install target to the Makefile wrapping the documented command:

install:
	uv tool install --force .

--force makes the target an idempotent install-or-upgrade: each run reinstalls from the current checkout state (the documented "newest = current checkout" semantics).
Keep it decoupled from the check gate (fast, no surprise test runs); the gate remains a separate explicit step.
Document the target in the Makefile header comment and add it as the from-checkout alternative in the README "Installation" section.

Acceptance criteria

make install provisions or upgrades the three console commands (scarcity-router, scarcity-router-mcp, scarcity-router-server) in the isolated uv tool environment.
Running it twice succeeds (idempotent).
Makefile header documents the new target; README mentions it.
make check still passes.

## Problem There is no `make install` target. The documented installation path (README "Installation", D-034) is `uv tool install` from the checkout or a built wheel, but nothing in the Makefile wraps it, so upgrading means remembering the exact `uv tool install --force` invocation (and that `uv tool upgrade` does not apply to path-installed tools). ## Proposal Add an `install` target to the Makefile wrapping the documented command: ```make install: uv tool install --force . ``` - `--force` makes the target an idempotent install-or-upgrade: each run reinstalls from the **current checkout state** (the documented "newest = current checkout" semantics). - Keep it decoupled from the `check` gate (fast, no surprise test runs); the gate remains a separate explicit step. - Document the target in the Makefile header comment and add it as the from-checkout alternative in the README "Installation" section. ## Acceptance criteria - [ ] `make install` provisions or upgrades the three console commands (`scarcity-router`, `scarcity-router-mcp`, `scarcity-router-server`) in the isolated uv tool environment. - [ ] Running it twice succeeds (idempotent). - [ ] Makefile header documents the new target; README mentions it. - [ ] `make check` still passes.