In-editor aids

Overview

The plugin entry point (src/main.ts) connects four small, mostly import-free modules, but holds none of their logic itself:

• Field reference: src/fields.ts builds a FieldDoc[] (resolveFieldDocs). It pairs a fixed, editorial FIELD_ORDER list with descriptions pulled from the pinned vocabulary manifest src/lokf-vocab.json, which scripts/build-vocab.mjs fills from the schema, so the wording never forks from the schema. src/field-modal.ts’s FieldReferenceModal (a read-only SuggestModal) is the “Look up a LOKF field” command’s surface, because Obsidian’s Properties widget has no per-property description API.
• Inline trust marker: src/inline.ts is a CodeMirror 6 ViewPlugin. It decorates a concept’s frontmatter with its trust tier as you edit, driven by a TrustMarkerHost the plugin implements. It works in Source mode only, because Live Preview renders frontmatter through Obsidian’s own Properties widget instead.
• Frontmatter autocomplete: src/suggest.ts’s KtlCuratorSuggest (an EditorSuggest) offers values, never key names, inside a concept’s frontmatter. The pure, Node-tested src/suggest-context.ts (detectSuggestContext, withinFrontmatter) decides what kind of value is being typed (an actor, a status or a date), so the Obsidian-facing half stays thin.
• Shared trust-tier vocabulary: src/trust-label.ts’s trustLabel/handoffLabel (tones: confirmed | automation | unchecked | draft | retired) is the one wording that the status bar, the inline marker and the review card all render. It is derived from a TrustRecord (trust-engine.md) and never stored. A draft status gives the draft tone only while no person has confirmed the concept. A confirmed concept that a question set back to draft keeps the confirmed tone, and while the question waits its handoff hint reads “Reopened - a question waits for the curator”.