Quality: 119 tests: 119 passed, 0 failed, 0 skipped, 93 of 94 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the library
Repoctl, the operations program of a repository (commons repoctl 0001-repoctl-layers ; 0010-repoctl-host FR-003 ): the three layers of Kanon as namespaces, the entries of the program (repoctlProgram for a host that describes it, main for the command line) and what a repository's repoctl.config.ts is written with: defineConfig and the types of the configuration.
# Entry points# Modules# Examplesimport { defineConfig, governance, repoctlProgram } from "@intellectual-frontiers/repoctl" ;
governance.VERBS .sync.tier; // "contributor"
typeof repoctlProgram; // "function"
defineConfig ({ repo: "acme/app" , commit: { identity: { name: "A B" , email: "a@example.test" } } }).repo; // "acme/app" # LimitsWhat the modules of this area do not do, or do only in part, as each module's @limits says.
logical/hygiene.ts
src/logical/hygiene.ts
It does not know the names of the libraries of commons: a path is a path of commons where a segment is named commons, and a package under a folder is a vendored copy where its name is in the scope of commons and the folder is not the root package and not a workspace the root declares.
logical/prove.ts
src/logical/prove.ts
It plans T0 to T6 and runs nothing; the caller decides which tiers run where. A change it cannot classify is outside, and a change it cannot explain (Git that does not say) plans everything.
logical/select.ts
src/logical/select.ts
A test that reads a file by a path it builds at run time is found only where it names the checkout (CHECKOUT, import.meta, process.cwd): it is then environmental and runs whenever its library is proved.
logical/surface.ts
src/logical/surface.ts
A name is the key of a declaration, so two declarations of one name in two files of a library are one entry with both texts; an overload is one entry. A change that only moves a declaration to another file leaves its entry as it was.
physical/prove-run.ts
src/physical/prove-run.ts
The platform and release proofs do not run here. A failure is never cached, and a test that reads the checkout is never left out nor cached.
physical/prove.ts
src/physical/prove.ts
T4 runs the root tests that run hermetically; T5 and T6 are planned and left to CI, the nightly run and the release, because they need other systems or every library.
physical/tests.ts
src/physical/tests.ts
A test that reads a file by a path it builds at run time, outside the checkout's own names, is not seen by the imports; the cache would keep its pass after that file changed. Such a test is environmental by naming the checkout.