-
Notifications
You must be signed in to change notification settings - Fork 2
Plan v030 plumbing and tests
Current — completed plan; plans are frozen once written, a changed design gets a new plan.
All v0.2.0 work is closed and the roadmap is empty. An audit of the shipped
plugin surface found three real defects plus zero automated coverage of
scripts/okf-graph.py, which is the thing the plugin exists to do. Fix what is
broken, then leave a check behind so it stays fixed.
- Repo: https://github.com/SpillwaveSolutions/okf-plugin
- Released: v0.2.0 (only tag); v0.2.1 exists in generated docs but was never cut
- Hosts: Claude Code + Grok Build
Verified defects:
- The plugin's only hook has never run.
hooks/hooks.jsonpassed"$FILE_PATH", but Claude Code delivers the PostToolUse payload as JSON on stdin, sookf-curate.shbound an empty string and exited immediately on every edit. -
parse_frontmattersilently dropped standard YAML:tags:followed by- itemlines returned'', coerced to[]with no warning. The repo's own generators emit inline lists, so this was invisible in-repo and hit only user-authored bundles. - Mermaid node IDs came from the path stem, so all seven
index.mdfiles in sample-okf collapsed into one node andagents/foo.mdmerged withdocs/foo.md. - No tests existed anywhere, and CI never invoked the graph engine or sample-okf.
-
(P0) Fix the no-op post-edit hook and curate fallback Read the file path from the PostToolUse stdin JSON instead of a nonexistent $FILE_PATH, widen the matcher to include MultiEdit, and replace the grep-based fallback with the repo's own okf-graph.py validate (which also deletes a realpath -m call that is broken on stock macOS).
-
(P0) Fix okf-graph.py block-sequence YAML, Mermaid IDs, and add validate --strict Parse standard YAML block sequences in frontmatter; derive Mermaid node IDs from the full relative path via a shared mermaid_id/render_mermaid helper; add a --strict flag so CI can gate on warnings while the skills keep the lenient default.
-
(P0) Add tests/test_okf_graph.py and wire it into CI and pre-commit Plain-assert suite covering frontmatter parsing, link normalization, edge merging, Mermaid ID uniqueness, sample-okf validity, and version consistency across the four manifests. Runs in CI and as a guarded pre-commit check.
-
(P1) Qualify intra-plugin paths with CLAUDE_PLUGIN_ROOT Command files referenced skills by bare relative path, which does not resolve in a consuming project. Annotate repo-local bin/worklog references honestly rather than pretending they resolve from the plugin root.
-
(P2) Add graph subcommand and the two missing slash commands Back the okf-visualize skill with a real graph subcommand (mermaid/json/html) built on the shared emitter, and add commands for okf-visualize and okf-maintain so all seven skills have a command. Non-blocking for the release.
-
(P2) Release chore — bump to 0.3.0 across the four manifests and README The version lives in four places and drifts silently; the new test asserts they agree.
- Index-Releases
- Latest snapshot: Roadmap-2026-08-03_v0.3.2-release
- Index-Status
- Index-Decisions