engineering-memory 0.2.0 → 0.2.2

package/bin/engineering-memory.mjs

@@ -29,8 +29,6 @@ Choose the hook mode through the Codex or Claude native questionnaire before
 passing a repository. The installer never opens a questionnaire or an
 authentication web page.`;
 
-// The backend this package was published for. An installation only names one
-// when it points at a different, self-hosted backend.
 async function publishedApiUrl() {
   const manifest = await readJson(join(packageRoot, 'package.json'));
   const apiUrl = manifest?.engineeringMemory?.apiUrl;

package/lib/stage-runtime.mjs

@@ -3,10 +3,6 @@ import { tmpdir } from 'node:os';
 import { dirname, join } from 'node:path';
 import { readJson, resolveProductionPackagePaths } from '../install/files.mjs';
 
-// The published package cannot carry node_modules, because npm excludes it from
-// every tarball. The bridge runtime is assembled here from the dependencies npm
-// installed for this package, into the exact layout the installer verifies
-// against the bridge lockfile.
 export async function stageBridgeRuntime(packageRoot, resolver) {
   const source = join(packageRoot, 'runtime');
   const packageJson = await readJson(join(source, 'package.json'));
@@ -37,8 +33,6 @@ export async function stageBridgeRuntime(packageRoot, resolver) {
   return staged;
 }
 
-// A package is free to keep package.json out of its exports map, and several do,
-// so the directory is found on disk rather than through module resolution.
 async function locate(name, resolver) {
   for (const directory of resolver.resolve.paths(name) ?? []) {
     const candidate = join(directory, ...name.split('/'));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "engineering-memory",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "Installs the Engineering Memory skill and its local MCP bridge. Sign in after installing; your organization and project are resolved from your account.",
   "license": "UNLICENSED",
   "type": "module",

package/runtime/dist/src/runtime/bridge-service.js

@@ -1160,9 +1160,6 @@ export class BridgeService {
             });
         });
     }
-    // What the backend expects of this client, and whether the user has already
-    // been asked about it. A required update leaves no choice; an optional one is
-    // offered once per version and never raised again after a refusal.
     async clientUpdate(authenticated) {
         const installed = this.dependencies.clientVersion;
         if (!authenticated) {
@@ -1799,8 +1796,8 @@ export class BridgeService {
         if (pointer.verificationIntent || pointer.closeIntent) {
             throw new Error('A clean active task snapshot is required for checkpointing');
         }
-        if (pointer.taskSlug !== input.taskSlug) {
-            throw new Error('Checkpoint task slug does not match the active task pointer');
+        if (pointer.taskSlug.toLowerCase() !== input.taskSlug.toLowerCase()) {
+            throw new Error(`Checkpoint task slug ${input.taskSlug} does not match the active task ${pointer.taskSlug}`);
         }
         return pointer;
     }
@@ -2296,7 +2293,19 @@ function assertNewResourceEvidence(candidates, evidence) {
         .map(({ path, kind }) => ({ path, kind }))
         .sort((left, right) => left.path.localeCompare(right.path));
     if (stableStringify(expected) !== stableStringify(actual)) {
-        throw new Error('New screen or shared component paths require exact memory reconciliation');
+        const expectedPaths = new Set(expected.map((entry) => entry.path));
+        const actualPaths = new Set(actual.map((entry) => entry.path));
+        const missing = expected
+            .filter((entry) => !actualPaths.has(entry.path))
+            .map((entry) => `${entry.path} (${entry.kind})`);
+        const extra = actual
+            .filter((entry) => !expectedPaths.has(entry.path))
+            .map((entry) => `${entry.path} (${entry.kind})`);
+        const details = [
+            missing.length ? `missing evidence for ${missing.join(', ')}` : '',
+            extra.length ? `evidence for paths the policy does not classify: ${extra.join(', ')}` : '',
+        ].filter(Boolean);
+        throw new Error(`New screen or shared component paths require exact memory reconciliation. ${details.length ? details.join('; ') : 'The kinds do not match the project discovery policy.'}`);
     }
 }
 function assertValidationEvidence(validations) {

package/runtime/dist/src/runtime/repository-decision-store.js

@@ -1,8 +1,5 @@
 import { join } from 'node:path';
 import { readJson, removeFile, writeJson } from '../utilities/files.js';
-// What a user decided about Engineering Memory in one repository, on one
-// machine. It never lives in the repository: a developer switching it off must
-// not switch it off for everyone who clones after them.
 export class RepositoryDecisionStore {
     root;
     queues = new Map();

package/runtime/dist/src/runtime/update-choice-store.js

@@ -1,7 +1,5 @@
 import { join } from 'node:path';
 import { readJson, writeJson } from '../utilities/files.js';
-// Which client version the user was offered and turned down. Asking again for
-// the same version is nagging; asking when a newer one arrives is news.
 export class UpdateChoiceStore {
     path;
     root;

package/skill/references/questionnaires.md

@@ -68,6 +68,12 @@ Before proposing a flow record, ask the user what the design cannot answer: whic
 
 When the user names a different Figma file or link, treat it as a correction to the `figma_reference` record and propose the revision in the same reply, with the new file key and URL. Ask for approval there and then. Do not carry the new address only in the conversation: the next session reads the record, not the chat.
 
+## Running the Application
+
+When the change is something a person sees or interacts with and this environment can run the application, ask before launching it rather than starting on your own. A run occupies the user's machine, can take minutes, and they may be using it. Say what you would exercise and what you are looking for, so the answer is about the work rather than about the tooling.
+
+Ask again nothing when they decline. Verify what you can without it and state in the handoff that the flow was not exercised in a running application.
+
 ## Correction Scope
 
 At a natural checkpoint after recording and fixing a user correction, first state how the correction was classified and why, then offer the scopes that classification allows.
@@ -99,6 +105,8 @@ After `task.close`, and every time, ask the user what to do with the finished wo
 
 The two pull request options take the base branch the pull request targets, typed by the user; the head is the branch the task was done on. Never guess a base branch, and never open a pull request that was not asked for.
 
+Check that a pull request can actually be opened before offering one. If the machine has no `gh` and no token to open it with, say so in the option itself and offer what is really on the table: commit and push, and the ready-to-open compare link afterwards. Offering something you cannot deliver wastes the user's answer. Never read a credential out of a keychain or a helper to open one yourself.
+
 Once a pull request exists the work is not finished and the turn does not end there. Check whether it merges cleanly. If it does, say so with the link. If it does not, name the conflicting files and ask whether to resolve them — then wait. Resolving a conflict is a change to someone else's work and needs its own yes.
 
 ## Git Hook