Module manager 

The manager axis: which tool manager a target obtains rk through.

One enum owns the list, and one detection reads which manager files a target carries. rk depend reads the same files to land another project, so both verbs share this module and a fifth manager is one variant here plus its rows in each matrix. The per-manager pin reader is pure text in, values out: it names whether a file mentions release-kit, the version it pins where the manager records one, and nothing it cannot read offline.

Structs

Entry

One manager’s entry in the status report: what its file says.

ManagerFile

One manager and the file that declares it.

Enums

Freshness

The offline freshness of a pinned version against this binary’s own: a fact the report carries, never a judgment.

Manager

A tool manager a project declares its development tools through.

PinRead

What one manager’s file says about the release-kit pin.

Constants

DEP_NAME

The name every manager file is read for.

MISE_FILES

The mise configuration paths, in mise’s precedence order, the highest first: a file, or a conf.d directory whose *.toml entries all load. A local override file is left out: it is not committed.

Functions

entries

One entry per manager, in ALL order, absent ones included: an absent manager is a fact, never a fault.

first_mention

The first line naming name as a word, 1-based.

manager_files

The manager files present, one per manager, in the closed order.

read_pin

Read one manager’s text for the release-kit pin.

rewrite_line

The same text with one line’s pinned version replaced: the first occurrence of from after the release-kit mention on that line. Only those bytes change; every other byte of the file survives.