IF Commons GitHub

Repoctl

14 specifications, 95 requirements. All libraries

0001 Repoctl layers

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/layers.test.ts: every file of the real tree is in a unit and a file in none is layers/unclassified
FR-002checkbun run verifysuite/layers.test.ts: below may not import above and each unit imports only what its row allows
FR-003checkbun run verifysuite/layers.test.ts: the package exports the library and its layers
FR-004checkbun run verifysuite/layers.test.ts: verify runs every check of the library
FR-005checkbun run verifysuite/layers.test.ts: the version of the program, the manifest, the package and the record agree
FR-006checkbun run verifysuite/layers.test.ts: no source of Governance or Logical imports a module that does input or output

0002 Repoctl governance

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/governance.test.ts: each identity is made only by its constructor, which says why a text is not one
FR-002checkbun run verifysuite/governance.test.ts: every verb is in the table and no verb contradicts its facts or its reach
FR-003checkbun run verifysuite/governance.test.ts: the ladder has three tiers and each verb is at its tier
FR-004checkbun run verifysuite/governance.test.ts: every code has an explanation and the catalogue is valid
FR-005checkbun run verifysuite/governance.test.ts: the table of generators names a command, inputs and outputs for each, and every generator with a --check of the repository is in it
FR-006checkbun run verifysuite/governance.test.ts: the table of checks has a command and a code for each

0003 Repoctl sync, merge and check

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/sync.test.ts: the order puts a reader after its writer and refuses generators that wait for each other
FR-002checkbun run verifysuite/sync.test.ts: only a stale generator is run, it is checked again, and a failure of one does not stop the others
FR-003checkbun run verifysuite/sync.test.ts: --check writes nothing and names the stale generator with its command; the real repository passes
FR-004checkbun run verifysuite/sync.test.ts: a second run changes no file, and --only runs only what it names
FR-005checkbun run verifysuite/merge.test.ts: in a real repository a conflict in a generated file is made again, one in a file that holds written text keeps the lines of both sides, and a conflict in a written file is left as Git left it
FR-006checkbun run verifysuite/merge.test.ts: the merge commit is made only where no conflict is left, and a refusal of Git is E-MERGE-FAILED
FR-007checkbun run verifysuite/check.test.ts: one report with a code and a fix for each finding, the real repository passes, nothing is written
FR-008checkbun run verifysuite/check.test.ts: a constant that disagrees with its library's version is found, and so is one the manifest names that is missing
FR-009checkbun run verifysuite/check.test.ts: every code is explained and a text that is no code names the nearest
FR-010checkbun run verifysuite/declared.test.ts: a package or a node: import that the manifest does not declare is found with its file and line; the library itself, relative and bun: imports and block comments are not; the real repository declares every import

0004 Repoctl status and release

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/status-release.test.ts: a row has the three versions and a state, as a table and as JSON, from a real repository with real tags
FR-002checkbun run verifysuite/status-release.test.ts: --offline asks no registry and reads the local tags
FR-003checkbun run verifysuite/status-release.test.ts: a version npm does not list is shown as not listed, and an unreachable registry is a warning
FR-004checkbun run verifysuite/status-release.test.ts: the plan of a real repository is given and nothing is written
FR-005checkbun run verifysuite/status-release.test.ts: apply writes the version into the constant the manifest names and the generators are made again
FR-006checkbun run verifysuite/status-release.test.ts: the preview prints the phrase, and a wrong phrase or no token sends nothing
FR-007checkbun run verifysuite/status-release.test.ts: the token is in no stream, outcome or argument
FR-008checkbun run verifysuite/status-release.test.ts: the npmrc is 0600, outside the repository and removed after a success and after a failure
FR-009checkbun run verifysuite/status-release.test.ts: npm is given an absolute path of the tarball
FR-010checkbun run verifysuite/status-release.test.ts: each release is tried in order, a failure is reported and the staging is said

0005 Repoctl library, commit and doctor

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/library-commit-doctor.test.ts: the scaffold has every file, and a library made in a copy of the repository passes its verify
FR-002checkbun run verifysuite/library-commit-doctor.test.ts: an invalid, a reserved and an existing name are refused with their codes
FR-003checkbun run verifysuite/library-commit-doctor.test.ts: the role is written into the map of roles of the README and sync --check ends with 0
FR-004checkbun run verifysuite/library-commit-doctor.test.ts: in a real repository the commit has the identity as author and committer
FR-005checkbun run verifysuite/library-commit-doctor.test.ts: the trailers are in order, and a subject, an issue and an address that do not fit are refused
FR-006checkbun run verifysuite/library-commit-doctor.test.ts: a path of the agent, of installed packages and a secret are refused
FR-007checkbun run verifysuite/library-commit-doctor.test.ts: a stale generator refuses the commit, nothing staged is said, and the preview commits nothing
FR-008checkbun run verifysuite/library-commit-doctor.test.ts: each thing wrong with a checkout is a finding with its code, in order
FR-009checkbun run verifysuite/host.test.ts: --impact writes the line in its place, a word that is none of the three and a configuration without the trailer are refused; suite/library-commit-doctor.test.ts: the message with the Impact line in order, and new library lists the spec kit in the configuration of the site

0006 Repoctl surfaces

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/surfaces.test.ts: every verb has examples and the model has no problem
FR-002checkbun run verifysuite/surfaces.test.ts: describe gives the elements of every verb, code and tool
FR-003checkbun run verifysuite/surfaces.test.ts: the tools of each tier are the verbs of that tier, a hidden tool is refused with its reason and a destruction is only a preview
FR-004checkbun run verifysuite/surfaces.test.ts: the reach of each action, and the confirmation is for a person alone
FR-005checkbun run verifysuite/surfaces.test.ts: the tier is the host's, an unknown word ends with 2 and a verb of a higher tier is not there
FR-006checkbun run verifysuite/surfaces.test.ts: the root package has the script and the bin, and the launcher is there

0007 Repoctl hygiene

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/hygiene.test.ts: the verb is declared once with its facts and its examples and each code has an explanation
FR-002checkbun run verifysuite/hygiene.test.ts: each of the six findings is made from facts, in the order of the codes, and the repository of commons is not reported for its own packages
FR-003checkbun run verifysuite/hygiene.test.ts: bun.lock and package-lock.json give the same copies, the installed tree is read through the port and a lockfile that cannot be read is a finding
FR-004checkbun run verifysuite/hygiene.test.ts: the exit status is 1 only for a failure and --json is one document
FR-005checkbun run verifysuite/hygiene.test.ts: status asks npm for the package a library publishes
FR-006checkbun run verifysuite/hygiene.test.ts: a repository with no root package.json is judged folder by folder: the lockfile and node_modules next to each package.json are read, two folders are never one install, and a folder with dependencies and no lockfile is named
FR-007checkbun run verifysuite/history.test.ts: the identity of the merge commits is checked by a pure function and by the verb in a real Git repository, a held hash is not reported and a stale one is a warning, and the merge of repoctl merge is the configured identity

0008 Repoctl prove

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/prove.test.ts: the verb prints the plan as JSON, refuses a tier that is none with 2, and ends with 1 where a proof fails
FR-002checkbun run verifysuite/prove.test.ts: the tiers are a closed set with a budget and each proof belongs to exactly one
FR-003checkbun run verifysuite/prove.test.ts: a changed file is classified by its path and its content at the base and now
FR-004checkbun run verifysuite/prove.test.ts: each class plans the proofs its row says, and only those
FR-005checkbun run verifysuite/prove.test.ts: a change to the planner or what Git cannot say plans every proof of every tier
FR-006checkbun run verifysuite/prove.test.ts: a source change with the same surface proves its library alone, over a real repository too
FR-007checkbun run verifysuite/prove.test.ts: the fingerprint ignores comments and bodies and names the declarations that changed
FR-008checkbun run verifysuite/prove.test.ts: a changed symbol reaches its importers by name through the surfaces that mention it
FR-009checkbun run verifysuite/prove.test.ts: every skipped proof has a reason of the closed union and a sentence; the plan is the same twice
FR-010checkbun run verifysuite/prove.test.ts: --all plans every tier and a change to the planner plans the same
FR-011checkbun run verifysuite/prove-select.test.ts: selection by imports, trace and symbols, environmental tests never left out, the cache keeps passes under an exact key and a second run takes them
FR-012checkbun run verifysuite/prove-select.test.ts: a foundation change plans the suites of every foundation library
FR-013checkbun run verifysuite/prove-select.test.ts: the quarantine record, its expiry, and the seeds of a failing property test
FR-014checkbun run verifysuite/prove-select.test.ts: the plan job writes the proof plan to the summary, the matrices are the planner of libraries and the full run is scheduled

0009 Repoctl configuration

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/config.test.ts: parseConfig makes the identities and lists every reason
FR-002checkbun run verifysuite/host.test.ts: the file is found above the working folder, and each failure is its typed problem
FR-003checkbun run verifysuite/host.test.ts: a fixture repository with a minimal configuration runs sync --check, check and merge; a function generator
FR-004checkbun run verifysuite/host.test.ts: commit with the configuration's identity, prefix and trailers
FR-005checkbun run verifysuite/host.test.ts: hygiene on the fixture with its own policy
FR-006checkbun run verifysuite/config.test.ts: the doctor policy and the variable names

0010 Repoctl host and capabilities

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/host.test.ts: no quoted path of the repository of commons in the source of the host
FR-002checkbun run verifysuite/host.test.ts: the capabilities turn verbs on and off
FR-003checkbun run verifysuite/package.test.ts: the packed tarball installed in a scratch project runs --help and doctor offline
FR-004checkbun run verifysuite/status-release.test.ts: a held library is held in the status

0011 Repoctl docs verbs

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/docs.test.ts: the verbs are there only with docs settings
FR-002checkbun run verifysuite/docs.test.ts: the generator is loaded from the repository and missing is its typed problem
FR-003checkbun run verifysuite/docs.test.ts: a failing generator is E-DOCS-FAILED
FR-004checkbun run verifysuite/docs.test.ts: serve answers on loopback only
FR-005checkbun run verifysuite/docs.test.ts: the generator is found in the one package first, then the per-library package, and the problem names both

0012 Questions of the repository in SQL

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/query.test.ts
FR-002checkbun run verifysuite/query.test.ts
FR-003checkbun run verifysuite/query.test.ts
FR-004checkbun run verifysuite/query.test.ts
FR-005checkbun run verifysuite/query.test.ts

0013 Steps of a pipeline under the build policy

RequirementMechanismWhoNote
FR-001checkbun test suite/ci.test.ts: the verb is in the table, local only, and comes where the capability is on
FR-002checkbun test suite/ci.test.ts: a failing command ends 0 with its finding kept, a wrong call ends 2

0014 What a consumer uses of the package

RequirementMechanismWhoNote
FR-001checkbun run verifysuite/usage.test.ts
FR-002checkbun run verifysuite/usage.test.ts
FR-003checkbun run verifysuite/usage.test.ts
FR-004checkbun run verifysuite/usage.test.ts
FR-005checkbun run verifysuite/usage.test.ts

Titles, headings, exports, tables, columns and requirements. Esc closes.