PlanOpticon v0.6.0 Is Live: Cleaner Output Contracts for Downstream Tools
PlanOpticon v0.6.0 is live.
This is not a flashy model release. It is a contract-cleanup release.
The CLI output, docs, and examples now match what the tool actually emits, which matters when those files are being consumed by other tools instead of read casually by a human once.
pip install -U planopticon
What Changed
- Batch CLI messaging now points to the root
manifest.json - Output format docs now match the current
knowledge_graph.jsonshape key_points.jsonandaction_items.jsonexamples now match the fields the tool emits- Exchange payload docs now show
versioninstead of an outdated schema field - Batch guides and troubleshooting pages now reference the current manifest layout
Why This Matters
When a tool is used by humans only, stale docs are annoying.
When it sits inside a pipeline, stale docs become bugs.
Downstream consumers infer formats from examples. Auto-detection depends on filenames. Integration code grows around whatever the docs say is canonical. If the docs drift from runtime behavior, every consumer pays for it.
v0.6.0 is about tightening that contract so the output is easier to trust.
What It Improves
PlanOpticon already produces structured outputs that are useful well beyond the original recording: transcript, diagrams, action items, key points, and a knowledge graph. But those artifacts only compound in value if other tools can ingest them predictably.
This release makes that handoff cleaner.
It also pairs directly with navegador v1.1.0, which now recognizes current PlanOpticon layouts more reliably on the consuming side.
Less Drama, More Stability
There are no splashy new flags here. No giant UX rewrite. No new model headline.
Just a more stable documented contract between what PlanOpticon writes and what downstream tools expect to find.
That kind of maintenance work rarely looks exciting in a changelog. It becomes exciting later, when nobody has to debug glue code at midnight.
