tools tier

tools-no-dark

HARVEST-PLAYBOOK Gate 3.4 no-dark check (ported from scripts/harvest/no-dark.sh via script-scan): a new crate must be referenced by >=1 host on the runtime path or it ships dark. Component-wise path exclusions (fixes the bash over-exclusion bug), bounded walk, in-process matching.

HARVEST-PLAYBOOK Gate 3.4 no-dark check (ported from scripts/harvest/no-dark.sh via script-scan): a new crate must be referenced by >=1 host on the runtime path or it ships dark. Component-wise path exclusions (fixes the bash over-exclusion bug), bounded walk, in-process matching.

Tiertools
Roleunclassified (baselined)
Pathcrates/tools/no-dark
Edition2021
Targetstools-no-dark
Public items0 across 0 modules
Tests11

What it is for

tools-no-dark — Gate 3.4: no capability ships dark (HARVEST-PLAYBOOK §13.6).

A new library crate must be referenced by >=1 HOST on the runtime path (not just its own tests). Prints the host references; if there are none, the capability ships dark, so the caller should open a wiring issue.

Usage: tools-no-dark infrastructure_jobs ~/projects (use the crate's Rust ident form, underscores: library crates_foo)

Capabilities

No public items.

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

No public modules: the crate root is its whole surface.

Public surface

No public items.

No pub use re-exports: every item above is declared in this crate.

Boundary

Depends on no other workspace tier.

Shares tier tools with 84 other crates: tools-advisory-reach, tools-archive-guard, tools-artifact-scaffold, tools-ask-ai-core, tools-ask-ais, tools-ask-gemini, tools-book, tools-book-report, … (84 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier (ontology)tools
Architectural role (taxonomy)unclassified (baselined)
Locationcrates/tools/no-dark
Vocabulary in force (lexicon)current

Dependencies

Runtime, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
anyhow^1noalways

Development. None.

Build. None.

Depended on by. Nothing in this workspace.

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

KindNameSource
bintools-no-dark`src/main.rs`

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

PropertyEvidence
async public surfacenone detected
async runtimenone detected
database accessnone detected
network I/Onone detected
unsafe codenone detected
environment variablesyes

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

VariableRead in
HOMEsrc/main.rs

No workspace crate depends on this one.

Verification

KindCount
Unit tests11
Integration tests0
Examples0
Doctests0

What the tests establish, by name:

Documentation coverage

MeasureDocumentedTotal
Public items with rustdoc00
Public modules with a //! block00

Metrics

MetricValue
Rust source files1
Source lines488
Code lines399
Public API items0
Public modules0
Tests11
Examples0
Cargo features0
Direct runtime dependencies1
Workspace reverse dependencies0
pie showData
    title Rust source composition
    "Code" : 399
    "Blank or comment" : 89

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.

All tools · Manual