Pathrule Core v0.3.1

Highlights

• Relevance decides the form, not only the order. The closest few entries are delivered as a full body and the rest as a name, an id and one line, so a correct ranking is never discarded for want of room.
• Skills are offered by name, whatever their rank. A memory is a fact and a rule is a constraint, but a skill is a procedure: injecting one unasked instructs the assistant rather than informing it.
• Rules earn their room. Rules now pass the same relevance test as everything else. A rule marked strict still keeps its body unconditionally.
• A team block in the compiled instruction files. The team, the person the file belongs to, who is the reference for which area, and declared decision scope. Names, paths, tags and a declared scope only, capped at a small token budget, and appended last so a membership change leaves the knowledge prefix byte identical.
• A pull ledger. Fetching something that was offered by name is recorded, and that label is what earns a full body on a later request. It performs file IO, so it is reachable only as a subpath import and never from the package barrel.

This snapshot is what @pathrule/cli@0.3.1 bundles.