The Ship Log
Changelog.
What changed in the kit, written for someone who has never seen it. Every entry leads with why you'd care, then what's new.
-
A Skill for Putting a Web App on iPhone and Android with Tauri
Agents can now walk a non-developer owner through wrapping their web app for phones, testing it, shipping it to testers and keeping it alive.
-
Survey: One Command for a Dashboard of Every context-v Folder
Graphify maps your code. Survey maps your context: what's in flight, what's stuck, what's a stub, and who's moving, at any scope.
-
Every Link Form Works, and Nothing Needs Converting
Obsidian wikilinks, with or without .md, and markdown links are all valid now. A new resolver shows where each one lands.
-
The Whole-Tree Survey Example Now Shows Public Repos Only
The live survey examples now show only repos that are public on GitHub, and every doc links to its file there.
-
Versions Can Have Three Parts or Four, and Agents Know Which Is Which
The kit no longer insists on four-part versions. Market-standard 0.1.0 is just as valid, and the user picks.
-
Epoch SemVer Joins the Version Formats
Keep the epoch without juggling two systems: 1002.3.0 is still a valid semver version, and nothing existing has to change.
-
Ledes Are Plain Text
Cards and previews show a lede raw, so backticks and asterisks appeared as literal symbols. The kit now says so, and sweeps remove them.
-
Scope the Survey to Any Repo and Everything Under It
One picker on every survey dashboard narrows the page to a pseudomonorepo and all its children, like astro-knots and every site in it.
-
Tagged, Iconed, and Submitted to the Claude Directory
v0.2.0 is the kit's first tagged release, and it's now in review for Claude's plugin directory, under a woodcut icon.
-
Fair Questions, Answered on the Landing Page
A new FAQ section answers the questions people actually ask about context-v: token cost, drift, regenerable code, and agents drowning in context.
-
Wikilinks Stay, and Your Config Says So
OKF never required a link style. Wikilinks stay the default, and context-v/config.md now declares the syntax a repo uses.
-
The Recommended Flow, Drawn
The landing page now shows the whole cycle in one picture: explore through reflect, then what the cycle taught you.
-
The Landing Page Leads With the Whole Idea
A dead simple, highly flexible, surprisingly effective pattern for context and memory: just add a context-v/ folder to every repo. Now it's the first thing you read.
-
The Kit Becomes a Plugin
Context Vigilance now installs into Claude Code from GitHub in two commands: the practice, seven workflow skills, and a frontmatter check.
-
The Kit Gets Its Own Front Door
A site for people adopting the kit: getting started in two commands, and twenty patterns explaining why context-v works the way it does.
-
Context-V Speaks the Open Knowledge Format
A decision, the kit's first: every context-v folder is an Open Knowledge Format bundle, and every doc's type is its folder's name.
-
Every Doc Knows Its Type, and Every Folder Has an Index
The OKF decision, built: every new doc carries its folder's type, every folder lists its docs, and /cv:upgrade pulls the latest kit.
-
The Kit Leaves the Corpus Behind
Installing the context-v plugin would have cloned 55 MB of our private history. So the kit got a fresh repo, and the corpus got a new name.