surface/api: classify deterministic and interactive entrypoints #463

New issue

Closed

opened 2026-04-27 19:59:26 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-04-27 19:59:26 +00:00

Problem

forge.nvim's user-facing surface is documented in pieces, but it still blurs deterministic command/helper entrypoints with interactive route and picker workflows.

Proposed solution

Classify every user-facing Ex and Lua entrypoint as deterministic core, deterministic UI, or interactive route/picker, then align docs, naming, and wrapper placement to that contract.

## Problem forge.nvim's user-facing surface is documented in pieces, but it still blurs deterministic command/helper entrypoints with interactive route and picker workflows. ## Proposed solution Classify every user-facing Ex and Lua entrypoint as deterministic core, deterministic UI, or interactive route/picker, then align docs, naming, and wrapper placement to that contract.

barrettruth commented

2026-04-27 20:18:00 +00:00

Fixed by merged PR #469.