@happyvertical/smrt-scanner 0.55.1 → 0.55.3

package/AGENTS.md

@@ -15,6 +15,23 @@ executes the source.
 - `ManifestAdapter` — converts resolved classes into the SMRT manifest shape
   (`toManifest()`); owns field-type inference (the `0` vs `0.0` integer/decimal
   heuristic, decorator interpretation, union/alias resolution).
+- Enum values (#3598): a field typed as a TS `enum` / `const enum` or a
+  string/number literal union (through aliases, imports within the scanned
+  project, `| null`, and unions that nest an alias) emits `enum: [...]` on its
+  manifest entry — declaration order, values not member names. `enum-values.ts`
+  (`resolveEnumValues`) flattens the alias map; `extractTypeAliases` renders
+  enums with static string/number/negative/template initializers and
+  auto-increment (mixed or computed enums yield no alias, never a partial list).
+  `enum` is emitted only when the final column type is `text`/`integer`/
+  `decimal` and agrees with the value kind. **Column-type effect:** numeric
+  enums and unions that nest an alias (`Base | 'extra'`) previously fell to
+  `json` and now infer `integer`/`text`/`decimal` (a schema change for a
+  consumer that declares such a field; `@field({ type: 'json' })` keeps the old
+  column and drops `enum`); an enum with a computed member now yields `json`
+  instead of a partial string alias. The alias map is project-wide by
+  bare name, so two same-named types in one package collide (last file wins).
+  String enum values retain their decoded quotes, backslashes, whitespace
+  escapes, and Unicode exactly through alias resolution and manifest emission.
 - `parseFile` / `parseSource` — parse a single file or a source string to a
   `FileScanResult` (classes, errors, type aliases, SMRT imports). Each class
   carries the parser's `bodyStart` offset; core's library build inserts its
@@ -49,6 +66,18 @@ executes the source.
   `FieldTypeInference`, `AgentSurface`, `AgentSurfaceIntent`,
   `AgentSurfacePlaybook`, `AgentSurfaceDiagnostic`.
 
+## The recipe matcher (#3590)
+
+`src/recipes.ts` finds classes extending `SmrtRecipe` (import-binding aware,
+aliases and namespaces included), reads their statics structurally, and
+resolves `models` class references through imports. `resolve()` fills
+`ScanResults.recipes` and appends validation errors to `results.errors`; pass
+`recipes` to `ManifestAdapter.toManifest` to emit the qualified `recipes` array.
+`static help` names a Markdown file beside the recipe; `resolve()` reads it and
+emits `help: { markdown, fieldRefs }` (`deriveHelpFieldRefs`, mirrored by core's
+`extractFieldRefs` and re-checked at manifest generation). Contract and rules:
+core's [agents/recipes.md](../core/agents/recipes.md).
+
 ## The agent-surface matcher (#2591)
 
 `@smrt()` classes are found by matching DECORATORS. A view intent (#2588) and a
@@ -232,6 +261,8 @@ place, `toKnowledgeAgentSurface` in `vite-plugin/index.ts`.
 - `src/agent-surface.ts` — the `defineIntent` / `definePlaybook` matcher, its
   diagnostics, `mergeAgentSurfaces` (#2591), and `checkAgentSurfaceToolNames`
   (#2725).
+- `src/recipes.ts` — the `SmrtRecipe` matcher, class-reference resolution,
+  and recipe validation (#3590).
 - `src/source-location.ts` — `getLineColumn`, split out so `agent-surface.ts`
   can resolve a diagnostic's position without importing `oxc-parser.ts`, which
   imports it back.