lemmafit 0.2.0 → 0.2.2

package/README.md

@@ -31,9 +31,9 @@ claude
 
 ## Use Cases / Considerations
 
-- lemmafit works with greenfield projects only. You must begin a project with lemmafit. Support for existing codebases is in the pipeline. 
+- lemmafit works with greenfield projects. You typically begin a project with `lemmafit init` though `lemmafit add` provides rudimentary support for existing codebases.
 
-- lemmafit compiles Dafny to Typescript which then hooks into a React app. In the future, we will support other languages and frameworks. 
+- lemmafit compiles Dafny to Javascript/Typescript which then hooks into a runtime like a React app. In the future, we will support other languages.
 
 - lemmafit is optimized to work with Claude Code. In the future, lemmafit will be agent-agnostic. 
 
@@ -44,7 +44,7 @@ claude
 2. The agent will write a `SPEC.yaml` and write verified logic in `lemmafit/dafny/Domain.dfy`
 3. The **daemon** watches `.dfy` files, runs `dafny verify`, and on success compiles to `src/dafny/Domain.cjs` + `src/dafny/app.ts`
 4. The agent will hook the generated TypeScript API into a React app — the logic is proven correct
-5. After proofs complete, run custom command in Claude Code `/guarantees` to activate claimcheck and generate a guarantees report
+5. After proofs complete, run the `/guarantees` skill to activate claimcheck and generate a guarantees report
 
 ## Project Structure
 
@@ -57,6 +57,7 @@ my-app/
 │   │   └── Replay.dfy           # Generic Replay kernel
 │   ├── .vibe/
 │   │   ├── config.json           # Project config
+│   │   ├── modules.json          # Module registry (for multi-module projects)
 │   │   ├── status.json           # Verification status (generated)
 │   │   └── claims.json           # Proof obligations (generated)
 │   └── reports/
@@ -75,6 +76,7 @@ my-app/
 
 ```bash
 lemmafit init [dir]                # Create project from template
+lemmafit add [Name]                # Add a verified module to an existing project
 lemmafit sync [dir]                # Re-sync system files (.claude/, hooks)
 lemmafit daemon [dir]              # Run verification daemon standalone
 lemmafit logs [dir]                # View daemon log
@@ -94,5 +96,6 @@ npm update lemmafit
 
 - Node.js 18+
 - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI
+- [claimcheck](https://github.com/metareflection/claimcheck) (`npm install -g claimcheck`) — needed for the `/guarantees` skill
 
 Dafny and dafny2js are downloaded automatically during `npm install` to `~/.lemmafit/`.

package/blank-template/package.json

@@ -19,7 +19,7 @@
     "@types/react": "^18.2.0",
     "@types/react-dom": "^18.2.0",
     "@vitejs/plugin-react": "^4.2.0",
-"typescript": "^5.3.0",
+    "typescript": "^5.3.0",
     "vite": "^5.0.0"
   }
 }

package/cli/generate-guarantees-md.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 /**
- * Generates lemmafit/.vibe/guarantees.md deterministically from:
- *   - lemmafit/.vibe/guarantees.json (claim-to-spec mapping)
+ * Generates reports/guarantees.md deterministically from:
+ *   - reports/guarantees.json (claim-to-spec mapping)
  *   - lemmafit/.vibe/claimcheck.json (claimcheck results, optional)
  *   - SPEC.yaml (for trusted entries and group info)
  *

package/cli/lemmafit.js

@@ -99,7 +99,8 @@ function initProject(targetDir, templateName, serverBase) {
   }
   config.secret = secret;
   if (serverBase.toLowerCase() !== 'none') {
-    const serverWsUrl = `${serverBase}/ws?project=${encodeURIComponent(projectName)}`;
+    const sep = serverBase.includes('?') ? '&' : '?';
+    const serverWsUrl = `${serverBase}${sep}project=${encodeURIComponent(projectName)}`;
     config.server = serverWsUrl;
   }
   fs.writeFileSync(configPath, JSON.stringify(config, null, 2));

package/cli/sync.js

@@ -110,19 +110,6 @@ function syncProject(targetDir) {
     fs.writeFileSync(claudeMdPath, POINTER_LINE + '\n');
   }
 
-  // Sync .claude/commands/ from package
-  const srcCommands = path.join(__dirname, '..', 'commands');
-  if (fs.existsSync(srcCommands)) {
-    const commandsDir = path.join(claudeDir, 'commands');
-    fs.mkdirSync(commandsDir, { recursive: true });
-    for (const file of fs.readdirSync(srcCommands)) {
-      fs.copyFileSync(
-        path.join(srcCommands, file),
-        path.join(commandsDir, file)
-      );
-    }
-  }
-
   // Sync .claude/skills/ from package
   const srcSkills = path.join(__dirname, '..', 'skills');
   if (fs.existsSync(srcSkills)) {

package/docs/CLAUDE_INSTRUCTIONS.md

@@ -60,6 +60,10 @@ When `modules.json` exists:
  - `lemmafit-proofs`: Load this skill before writing or editing lemmas
  - `lemmafit-react-pattern`: Load this skill before writing React 
  - `lemmafit-spec`: Load this skill when user asks to add or edit feature, and before writing or editing the spec.yaml file 
+ - `lemmafit-guarantees`: Load this skill to generate a human-readable guarantees report from proven Dafny code and verify claims with claimcheck
+ - `lemmafit-pre-react-audits`: Load this skill before writing React to audit proof strength and catch unverified logic
+ - `lemmafit-post-react-audit`: Load this skill after writing React to catch effect-free logic that should be in Dafny
+
 
 If you try to read any of these files and they are missing, alert the user. 
 

package/package.json

@@ -15,14 +15,13 @@
     "verified",
     "proof"
   ],
-  "version": "0.2.0",
+  "version": "0.2.2",
   "type": "commonjs",
   "files": [
     "cli/",
     "lib/",
     "docs/",
     "skills/",
-    "commands/",
     "kernels/",
     "blank-template/"
   ],
@@ -40,10 +39,12 @@
     "postinstall": "node ./cli/sync.js && node ./cli/download-dafny2js.js && node ./lib/download-dafny.js"
   },
   "dependencies": {
-    "claimcheck": "^0.2.0",
     "js-yaml": "^4.1.1",
     "ws": "^8.18.0"
   },
+  "peerDependencies": {
+    "claimcheck": "^0.2.0"
+  },
   "engines": {
     "node": ">=18.0.0"
   },

package/skills/lemmafit-dafny/SKILL.md

@@ -6,7 +6,7 @@ description: Dafny code patterns and reference for lemmafit apps. Use when writi
 # Lemmafit Dafny
 
 ## When to Write Code in Dafny
-- ALL `verifiable:true` entries in the spec MUST be written in Dafny (do not write verifiable code directly in JavaScript or TypeSscript)
+- ALL `verifiable:true` entries in the spec MUST be written in Dafny (do not write verifiable code directly in JavaScript or TypeScript)
 
 ## Dafny Pattern Example
 

package/{commands/guarantees.md → skills/lemmafit-guarantees/SKILL.md}

@@ -1,10 +1,15 @@
+---
+name: lemmafit-guarantees
+description: Generate human-readable guarantees from proven Dafny code and verify them with claimcheck. Use after verification succeeds and SPEC.yaml is in sync with Dafny. Produces guarantees.json, claimcheck-mapping.json, runs claimcheck-multi, and generates guarantees.md report.
+---
+
 # Generate Guarantees and Run Claimcheck
 
 You are generating human-readable guarantees from proven Dafny code and verifying them with claimcheck.
 
 ## Step 0: Make sure the state of the project is verified
 
-Check `lemmafit/.vibe/status.json` for the current verification status.
+Check your context for verification status of the project.
 
 ## Step 1: Read project data
 
@@ -35,7 +40,7 @@ Analyze the claims from `claims.json` and map them to spec entries from `SPEC.ya
 
 ## Step 3: Write guarantees.json
 
-Write `lemmafit/.vibe/guarantees.json` with this format:
+Write `reports/guarantees.json` with this format:
 
 ```json
 {
@@ -117,15 +122,15 @@ Parse the claimcheck results and report:
 - **Disputed** — a discrepancy was found. Show the `discrepancy` text and `weakeningType` (tautology, weakened-postcondition, narrowed-scope, wrong-property).
 - **Error** — lemma not found in source. Check the lemmaName.
 
-**If any claims are disputed:** Suggest specific fixes to the Dafny code or the requirement text. If the user agrees, make the fixes, wait for re-verification, and re-run the guarantees process. 
+**If any claims are disputed:** Suggest specific fixes to the Dafny code or the requirement text. If the user agrees, make the fixes, wait for re-verification, and re-run the guarantees process.
 
 ## Step 8: Ensure all files up to date
 
-Once iteration is complete, compare `claimcheck-mapping.json` with `guarantees.json` to ensure they contain equivalent information. If there's a discrepancy, trace back to the Dafny code to find which is most accurate. Adjust the relevant file accordingly and re-run `/guarantees` command. Once confirmed, report that the files are in sync.  
+Once iteration is complete, compare `claimcheck-mapping.json` with `guarantees.json` to ensure they contain equivalent information. If there's a discrepancy, trace back to the Dafny code to find which is most accurate. Adjust the relevant file accordingly and re-run `/guarantees` command. Once confirmed, report that the files are in sync.
 
 ## Step 9: Generate guarantees.md via the script
 
-Do this only after Step 9 confirms that `claimcheck-mapping.json` and `guarantees.json` are in sync.  
+Do this only after Step 8 confirms that `claimcheck-mapping.json` and `guarantees.json` are in sync.
 
 Run the deterministic report generator:
 
@@ -133,6 +138,6 @@ Run the deterministic report generator:
 npx lemmafit-generate-guarantees
 ```
 
-This reads `lemmafit/.vibe/guarantees.json`, `lemmafit/.vibe/claimcheck.json`, and `SPEC.yaml` and writes `lemmafit/.vibe/guarantees.md`. Do NOT write this file manually — always use the script so the report matches the JSON exactly.
+This reads `reports/guarantees.json`, `reports/claimcheck.json`, and `SPEC.yaml` and writes `reports/guarantees.md`. Do NOT write this file manually — always use the script so the report matches the JSON exactly.
 
-Report to the user: "A report of your app's guarantees has been generated in lemmafit/reports/guarantees.md" 
+Report to the user: "A report of your app's guarantees has been generated in lemmafit/reports/guarantees.md"

package/skills/lemmafit-spec/SKILL.md

@@ -39,7 +39,7 @@ SPEC.yaml is a structured YAML file with an `entries` list. Each entry has:
 - `depends_on` — list of spec IDs this entry depends on
 - `verifiable` — whether this can be proven in Dafny 
 - `guarantee_type` — `verified`, `assumed`, or `trusted`
-- `state` - `DRAFT`, `ADDRESSED`, `null`- only use `addressed` if the corresponding Dafny module or property have been verified. Use null for `verifiable: false`
+- `state` - `DRAFT`, `ADDRESSED`, `null` — only use `ADDRESSED` if the corresponding Dafny module or property have been verified. Use `null` for `verifiable: false`
 
 ### Example
 ```yaml
@@ -54,7 +54,8 @@ entries:
     module: AppCore
     depends_on: []
     verifiable: true
-    status: verified
+    guarantee_type: verified
+    state: ADDRESSED
   - id: spec-002
     req_id: null
     title: The increment button displays the current count