Metadata-Version: 2.4
Name: rn-forge-tooling
Version: 0.3.1
Summary: Developer-tool lifecycle verbs and install mechanics for the rn-forge-* CLIs
Author: Rohit Narayanan
Author-email: Rohit Narayanan <rohit.nn@gmail.com>
License-Expression: MIT
License-File: LICENSE
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.14
Classifier: Typing :: Typed
Requires-Dist: rn-forge-commons>=0.8.0,<0.9
Requires-Dist: rn-forge-cli>=0.1.1,<0.2
Requires-Dist: assertpy>=1.1 ; extra == 'testing'
Requires-Dist: pytest>=9.1.1 ; extra == 'testing'
Requires-Python: >=3.14
Project-URL: Documentation, https://rn-forge.github.io/pykit/packages/rn-forge-tooling/latest/
Project-URL: Source, https://github.com/rn-forge/pykit/tree/main/packages/rn-forge-tooling
Project-URL: Changelog, https://github.com/rn-forge/pykit/blob/main/packages/rn-forge-tooling/CHANGELOG.md
Project-URL: Issues, https://github.com/rn-forge/pykit/issues
Provides-Extra: testing
Description-Content-Type: text/markdown

# rn-forge-tooling

[Documentation](https://rn-forge.github.io/pykit/packages/rn-forge-tooling/latest/)
·
[Changelog](https://github.com/rn-forge/pykit/blob/main/packages/rn-forge-tooling/CHANGELOG.md)
·
[Source](https://github.com/rn-forge/pykit/tree/main/packages/rn-forge-tooling)
· [All pykit packages](https://rn-forge.github.io/pykit/)

The lifecycle and install layer of the developer-tooling stack: for command-line
tools that install themselves and manage their own versions. File generation,
local state and templates live in `rn-forge-commons`.

Where
[`rn-forge-commons`](https://github.com/rn-forge/pykit/tree/main/packages/rn-forge-commons)
is runtime-neutral — safe in a web server, a worker or a container — and
[`rn-forge-cli`](https://github.com/rn-forge/pykit/tree/main/packages/rn-forge-cli)
is the command-line shape every application wants, this package is deliberately
workstation-shaped: it assumes a developer's filesystem and a tool that owns
files in it. It owns:

- `install` — the tool lifecycle: `$RNF_HOME` layout (`ToolHome`), release
  sources and verification, archive extraction, the `ToolProduct` seam, and
  the transactional
  `install`/`upgrade`/`uninstall`/`cleanup`/`status`/`doctor` verbs.
- `cli` — `build_tool_app`, which builds an `rn-forge-cli` application from a
  `[cli]` table and adds the lifecycle verbs declared in a `[lifecycle]`
  table.

A repository that only needs a command line takes `rn-forge-cli` and stops
there. A package that ships into a deployed runtime (`rn-forge-django`,
`rn-forge-fastapi`) must never depend on this package outside a `codegen` extra.
Tooling may import cli and commons; neither may import tooling, and
`uv run lint-imports` proves it.

## Install

Require the package by version range:

```toml
[project]
dependencies = ["rn-forge-tooling>=0.3,<0.4"]
```

`rn-forge-cli` and `rn-forge-commons` come with it, as version ranges.

## Docs

Full API reference and guides are built with mkdocs:

```bash
uv run --group docs mkdocs serve   # or `mkdocs build`
```

Source lives in
[`docs/`](https://github.com/rn-forge/pykit/tree/main/packages/rn-forge-tooling/docs),
configured via
[`mkdocs.yml`](https://github.com/rn-forge/pykit/blob/main/packages/rn-forge-tooling/mkdocs.yml).

## Development

From the repo root or this directory:

```bash
uv run pytest packages/rn-forge-tooling
uv run ruff check packages/rn-forge-tooling
uv run pyright
```
