ICOR for Life - Scaffold Check

Is your vault up to date with the ICOR for Life Scaffold, and is what it has still intact? This plugin compares your vault with the latest scaffold version, read-only, and writes a report you can work through by hand or hand to your AI.

Beta release. It works and is in daily use in a real vault, but you will find rough edges. If something looks off, open an issue on this repo and it gets fixed fast.

What it does

1. Reads your vault's own version. Every scaffold from 1.5.0 carries a .icor-for-life/ folder: VERSION says which version your copy was made from, and manifest.json describes that version as data.
2. Fetches the latest version's manifest from the URL in settings.
3. Compares, and reports three things a version number alone cannot:
   • Canonical files. For each file the scaffold ships, one of three answers: missing (copy it in), changed upstream since you installed (safe to update, you never touched it), or edited by you (keep it; the check never overwrites an edited file). Your own files, the ones the scaffold never shipped, are not drift and are not counted.
   • Leftovers. Files the scaffold removed or moved after your version that are still in your vault, each with the changelog line that says where it went. The three CSS snippets that moved into the theme in 1.5.0 are the founding case: a vault updated by hand keeps the files and keeps them enabled, and paints every rule twice.
   • Structure. The rooms the scaffold relies on exist, the plugins it expects are installed and enabled, every Base points at a folder that is there, and every enabled CSS snippet has its file.
4. Shows the result as a dot in the status bar (green ok, orange attention, red broken), a summary when you click it, and a report note.

What it never does

It never changes a scaffold file. The only things it writes are the report note (one per day, in a folder you choose) and its own data.json. Deleting a leftover, updating a file, enabling a plugin: those are yours to do, or your AI's. The report ends with a prompt you can paste into your AI session to have the fixes carried out, one change at a time, with the same rules the report follows.

The report

06 AI Team/AI Team Knowledge/Scaffold Check/YYYY-MM-DD-scaffold-check.md by default. Frontmatter carries health, installed_version, latest_version and the counts, so a Base or a script can read it. The body groups findings by what to do: Broken first (structure the scaffold relies on), then Attention (things to do), then Info (worth knowing). Each finding names the file, says what was found, and says what to do.

Settings

A check that cannot fetch the latest manifest says so in the status bar (grey, "offline") and does not guess.

For scaffold maintainers

The manifest is built by the scaffold's own Scripts/build-scaffold-manifest.py and checked by its release build. This plugin reads schema 1: version, rooms, plugins, snippets, files (path, sha256, kind, example), bases, and history (per version: removed with a note, renamed, added). A removal without a note fails the scaffold's own check before it ever reaches a member, which is the property this whole design rests on: the reason a file went is written down once, by the person who removed it, and every vault reads that one line.

Tests

npm test runs the engine against in-memory vaults: every defect the plugin exists to find is planted and must be found, and a clean vault must produce no findings. The red cases come first.

Licence

See LICENSE. Source-available under the ICOR for Life membership.