Skip to main content

Module report

Module report 

Source
Expand description

Read-only verbs. Every function returns its text instead of printing, so a CLI, an MCP server, and a library caller share one implementation.

Re-exports§

pub use crate::related::related;

Structs§

CheckReport
Outcome of check: the findings, and how many were errors.

Constants§

GRAPH_FOOTER
The line that closes a DOT document.
GRAPH_HEADER
The whole blocker and parent graph as Graphviz DOT. Node fill encodes state.
ROADMAP_HEADER
A markdown roadmap grouped by project and state. Closed items collapse into one section so the document stays about live work.

Functions§

agenda
Dated open work in the next days days plus anything overdue, grouped the way Org does: deadline, then scheduled, then appointment.
agenda_in
agenda over a corpus the caller already holds; see list_in.
ancestors
Transitive blocker ancestors, limited to a bounded number of hops.
backlinks
Every issue referring to target_id through a blocker edge, a parent link, a discovered-from or pivoted-to property, or a body mention. The relation is named on the row.
check
Validate the corpus: every parent and blocker id resolves, dates parse, open issues carry a creation date, and ids are unique across projects.
children
Issues whose :PARENT: points at parent_id.
claims
Every live claim, oldest first: the who-holds-what view. A claim is live while its issue is STARTED or BLOCKED (release happens on TODO, DONE, or CANCELLED), so this is the working set, not history.
consensus
The consensus over an issue’s ballots under the trust rows, printed beside the count so a reader sees where the weighting moved it.
consensus_anchored
consensus_with with per-agent susceptibilities laid over the configuration as well.
consensus_with
consensus with trust rows laid over the configuration.
count
The matching issue count and nothing else, for shell pipelines.
count_in
count over a corpus the caller already holds; see list_in.
cycles
Cycles in the blocker graph, one per line, or a line saying there are none.
export
One JSON object per line: every property, the logbook, the body, and the file line range. Round-trippable, and the seam other tools consume.
export_by_project
The same lines as export, grouped by project, from one read; a project’s text is byte for byte what export(layout, Some(project)) returns.
graph
A DOT graph of the corpus: one node per issue, blocker and parent edges.
graph_body
The nodes and edges of the graph, without the enclosing digraph block.
impact
Transitive issues waiting on this issue, limited to a bounded number of hops.
list
One row per issue: id, state, priority cookie, title.
list_in
list over a corpus the caller already holds, so a caller asking about several projects of one tracker loads it once.
plan_consensus
What a plan’s children settled on, child by child; never folded into one number, since a split child has no position and an unvoted one is absent.
ready
Actionable issues: TODO or STARTED with no open blocker.
ready_in
ready over a corpus the caller already holds; see list_in.
recall
The working set for one issue: the plan around it, the deeds its declared inputs produced, and its own. Derived from the graph, not ranked; related answers resemblance.
recall_deeds
The deed accessions recall found, inputs first, one per line, for deedar get $(vissue recall <id> --deeds-only).
roadmap
A markdown roadmap of active and closed work, with its title.
roadmap_body
The roadmap’s project sections, without the document title.
search
Case-insensitive substring scan over id, title, properties, and body.
show
One issue’s metadata, file range, and body text.
stale
Open issues whose :CREATED: is at least days old. An issue without a parseable date is never stale, because its age is unknown.
tree
Children and blockers below root_id, as indented text or Graphviz DOT.