Step note status

Two commands step the active Markdown note along the status chain none → open → closed by updating its frontmatter.

Why it matters

Note status is the small piece of frontmatter that moves work between Tasks Eye’s active and finished states. Editing YAML manually interrupts review, especially when the next transition is usually just one step along the lifecycle.

Two stepping commands keep that transition fast and predictable. Tasks Eye: Set note status: Next advances the note and Tasks Eye: Set note status: Previous moves it back along the ordered chain none → open → closed. Stepping back from open clears the property entirely, and the ends clamp so the note never wraps around. They use Obsidian’s frontmatter writer so other properties and note content remain intact.

Status belongs to the note, not its checkboxes. Closing a note therefore does not silently complete unfinished tasks; Tasks Eye’s existing Inbox validation continues to expose that inconsistency for deliberate repair.

What to expect

The previous and next status commands are registered without default hotkeys.
The next command moves the note one step forward and the previous command moves it one step back along none → open → closed.
Stepping back from open removes the status property entirely; stepping forward from no status sets open.
The ends clamp: forward from closed and back from no status do nothing.
An unsupported status value is repaired: forward sets open and back removes the property.
The commands work in editing and reading views for any active Markdown note, including notes outside the configured notes folder.
Other frontmatter properties, note content, and task checkboxes are preserved.
Invalid YAML is left untouched and produces an error notice.

What it looks like

Step the active note forward to Closed

Obsidian note showing a project whose status property is closed after stepping forward from open in Dark Minimal — Step the active note forward to Closed · Dark Minimal