@majeanson/lac 3.4.5 → 3.5.1

package/dist/lsp.mjs

@@ -8861,6 +8861,10 @@ const FeatureSchema = object({
 	lastVerifiedDate: string().regex(/^\d{4}-\d{2}-\d{2}$/, "lastVerifiedDate must be YYYY-MM-DD").optional(),
 	codeSnippets: array(CodeSnippetSchema).optional(),
 	implementationNotes: array(string()).optional(),
+	pmSummary: string().optional(),
+	testStrategy: string().optional(),
+	releaseVersion: string().optional(),
+	acceptanceCriteria: array(string()).optional(),
 	fieldLocks: array(FieldLockSchema).optional(),
 	featureLocked: boolean().optional()
 });

package/dist/mcp.mjs

@@ -3778,6 +3778,10 @@ const FeatureSchema$1 = object$1({
 	lastVerifiedDate: string$2().regex(/^\d{4}-\d{2}-\d{2}$/, "lastVerifiedDate must be YYYY-MM-DD").optional(),
 	codeSnippets: array$1(CodeSnippetSchema$1).optional(),
 	implementationNotes: array$1(string$2()).optional(),
+	pmSummary: string$2().optional(),
+	testStrategy: string$2().optional(),
+	releaseVersion: string$2().optional(),
+	acceptanceCriteria: array$1(string$2()).optional(),
 	fieldLocks: array$1(FieldLockSchema$1).optional(),
 	featureLocked: boolean$2().optional()
 });
@@ -8091,6 +8095,10 @@ object({
 	lastVerifiedDate: string().regex(/^\d{4}-\d{2}-\d{2}$/, "lastVerifiedDate must be YYYY-MM-DD").optional(),
 	codeSnippets: array(CodeSnippetSchema).optional(),
 	implementationNotes: array(string()).optional(),
+	pmSummary: string().optional(),
+	testStrategy: string().optional(),
+	releaseVersion: string().optional(),
+	acceptanceCriteria: array(string()).optional(),
 	fieldLocks: array(FieldLockSchema).optional(),
 	featureLocked: boolean().optional()
 });
@@ -8445,6 +8453,25 @@ Return ONLY a valid JSON array of plain strings — no other text, no markdown f
 
 If there are no notable implementation notes, return an empty array: []`,
 		userSuffix: "Extract free-form implementation notes for this feature."
+	},
+	pmSummary: {
+		system: `You are a product manager writing for a non-technical executive audience. Given a feature.json, write a 1–2 sentence business-value summary. Focus on the outcome and the user or business benefit — not the technical implementation. Avoid words like "component", "schema", "API", "TypeScript". Write as if you are telling a stakeholder why this feature matters. Return only the summary text, no JSON wrapper, no heading.`,
+		userSuffix: "Write a 1–2 sentence PM/exec summary for this feature."
+	},
+	testStrategy: {
+		system: `You are a software testing expert. Given a feature.json, describe in 2-4 sentences how this feature should be tested. Cover: what type of tests are appropriate (unit, integration, E2E, manual), what the hardest thing to test is, and any test setup or environment requirements implied by the feature. Be specific — name the actual components or flows that need coverage. Return only the strategy text, no JSON wrapper, no heading.`,
+		userSuffix: "Describe the test strategy for this feature."
+	},
+	releaseVersion: {
+		system: `You are a software engineering analyst. Given a feature.json, return the release version string this feature first shipped in, if it can be inferred from the statusHistory dates, revisions, or annotations. If not determinable, return an empty string. Return only the version string (e.g. "3.5.0", "v2", "2026-Q2") or an empty string — nothing else.`,
+		userSuffix: "Identify the release version this feature first shipped in, or return empty string if unknown."
+	},
+	acceptanceCriteria: {
+		system: `You are a software testing expert. Given a feature.json, break the successCriteria and problem statement into 3-8 discrete, testable acceptance criteria. Each criterion must be a single concrete, verifiable statement (e.g. "Camera roll permission prompt appears on first launch only", "Denying permission shows a recovery screen with an Open Settings button"). No vague statements. No compound criteria (one thing per item).
+
+Return ONLY a valid JSON array of strings — no other text:
+["criterion 1", "criterion 2", "criterion 3"]`,
+		userSuffix: "Generate structured acceptance criteria for this feature."
 	}
 };
 const JSON_FIELDS = new Set([
@@ -8455,7 +8482,9 @@ const JSON_FIELDS = new Set([
 	"npmPackages",
 	"publicInterface",
 	"externalDependencies",
-	"codeSnippets"
+	"codeSnippets",
+	"implementationNotes",
+	"acceptanceCriteria"
 ]);
 const ALL_FILLABLE_FIELDS = [
 	"analysis",
@@ -8465,6 +8494,9 @@ const ALL_FILLABLE_FIELDS = [
 	"tags",
 	"successCriteria",
 	"userGuide",
+	"pmSummary",
+	"testStrategy",
+	"acceptanceCriteria",
 	"domain",
 	"componentFile",
 	"npmPackages",
@@ -8472,7 +8504,8 @@ const ALL_FILLABLE_FIELDS = [
 	"externalDependencies",
 	"lastVerifiedDate",
 	"codeSnippets",
-	"implementationNotes"
+	"implementationNotes",
+	"releaseVersion"
 ];
 function getMissingFields(feature) {
 	return ALL_FILLABLE_FIELDS.filter((field) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@majeanson/lac",
-  "version": "3.4.5",
+  "version": "3.5.1",
   "description": "CLI for life-as-code — feature provenance tracking from the terminal",
   "license": "MIT",
   "repository": {