@llm4ts/shell 2.1.0 → 2.2.0

package/kits/j2ee-nextjs/packs/j2ee-nextjs-spa/pack.md

@@ -8,6 +8,7 @@ programs: .*\.jsp
 specs-dir: docs/modernization/specs
 features-dir: docs/modernization/features
 program-files: (?:src/app/<NAME>(?:/.*)?|src/services/<NAME>(?:/.*)?|contracts/<NAME>\.openapi\.yaml|tests/<NAME>\..*)
+feature-files: (?:src/services/<NAME>(?:/.*)?|contracts/<NAME>\.openapi\.yaml)
 
 ## Gates
 
@@ -47,3 +48,18 @@ unit: <jsp:include page="([^"]+)"
 
 files: .*web\.xml
 unit: <servlet-class>[a-z.]*\.([A-Za-z0-9]+)</servlet-class>
+
+## Survey: jsp-form-action
+
+files: .*\.jsp
+unit: action="([^"]+)"
+
+## Survey: jsp-ajax-target
+
+files: .*\.jsp
+unit: url:\s*['"]([^'"?]+)
+
+## Consolidate
+
+- cluster: jsp-form-action, jsp-ajax-target
+- context: jsp-include

package/kits/j2ee-nextjs/packs/j2ee-nextjs-spa/prompts/consolidate.md

@@ -0,0 +1,10 @@
+In a JSP portal a domain feature is the set of pages one servlet serves and
+one ESB service pair backs: a list page with its detail or edit form, the
+steps of one wizard (a session draft carried from step to step and a confirm
+screen), a read-only screen with its ajax refresh. The shell — header, nav,
+footer and any fragment every page includes — is one feature of its own,
+planned first because every other feature renders inside it. Filler pages
+with no form and no API call (help, profile, messages, settings) may be
+folded into one "Portal shell and static pages" feature; say so in the
+evidence. Never join two features that talk to different ESB services unless
+one page posts to the other's servlet.

package/kits/j2ee-nextjs/packs/j2ee-nextjs-spa/prompts/plan.md

@@ -1,17 +1,25 @@
-Derive the conversion task list for ONE page from its Page Spec. The
-destination is an existing Next.js SPA with a design system, an AuthProvider,
-and a port/adapter service convention — imitate it, never fight it.
+Derive the conversion task list for ONE domain feature from the Page Specs of
+its programs. The destination is an existing Next.js SPA with a design system,
+an AuthProvider, and a port/adapter service convention — imitate it, never
+fight it. The feature's included fragments (header, nav, footer) are context:
+use their specs for layout and navigation, do not re-implement them here
+unless this feature IS the shell.
 
-- Task 1: the anti-corruption service layer — the typed port interface under
-  src/services/<page>/port.ts matching the OpenAPI contract at
-  contracts/<page>.openapi.yaml (domain names only), a mock adapter under
-  src/services/<page>/mock.ts returning contract-shaped fixture data, and the
-  registry wiring. No page code yet.
-- Task 2: the page component(s) under src/app/<page>/ using ONLY the
-  destination design-system components and the port — forms, validation with
-  VERBATIM messages, navigation, and explicit state for anything the legacy
-  app carried in the session or hidden fields.
-- Task 3: component tests under tests/<page>.page.test.tsx in the house test
-  style — spec'd fields render, spec'd validations fire with their exact
-  messages, the port is called with contract-shaped payloads. Nothing else.
-- Each task names the spec rules and scenarios it covers.
+- Task 1: the feature's anti-corruption service layer — the typed port
+  interface under src/services/<feature>/port.ts matching the OpenAPI contract
+  at contracts/<feature>.openapi.yaml (domain names only, one operation per
+  API call across all the feature's pages), a mock adapter under
+  src/services/<feature>/mock.ts returning contract-shaped fixture data, and
+  the registry wiring. No page code yet.
+- Then ONE task per page of the feature, in navigation order (the page with no
+  inbound link inside the feature first; list before edit; step 1 before
+  step 2 before confirm): the page component(s) under src/app/<page>/ using
+  ONLY the destination design-system components and the feature port —
+  forms, validation with VERBATIM messages, navigation, explicit state for
+  anything the legacy carried in the session or hidden fields — together with
+  its component tests under tests/<page>.page.test.tsx in the house test style:
+  spec'd fields render, spec'd validations fire with their exact messages, the
+  port is called with contract-shaped payloads. Nothing else.
+- Each task names the programs, spec rules, and scenarios it covers. Scenarios
+  the decisions overlay marks drop, provided, or defer are out of scope: do
+  not plan them, and use the target capability a `provided` entry points at.

package/kits/j2ee-nextjs/packs/j2ee-nextjs-spa/prompts/refine-propose.md

@@ -0,0 +1,16 @@
+The target is an existing Next.js SPA with a design system, an AuthProvider, a
+router, and a port/adapter service convention. Things such a target usually
+PROVIDES, so a legacy page or scenario about them is a `provided` candidate
+once you have found the file that proves it:
+
+- login, logout, session timeout, and "remember me" — the AuthProvider and its
+  login route own these; a legacy login JSP is provided, not converted;
+- navigation shell, header, footer, and the nav link set — the app layout;
+- "back" links, breadcrumbs, and page titles — the router and layout;
+- session-carried drafts between wizard steps — client state, not a session;
+- client-side validation libraries — the house Form validation map.
+
+Things commonly DEPRECATED in a JSP estate, `drop` candidates when the spec
+itself shows the evidence (dead route, expired campaign, developer harness,
+print-only view, applet or Flash embed, frameset): name the evidence, never
+guess from the page name alone. Never propose `defer`.

package/kits/mainframe-java/packs/cobol-springboot/pack.md

@@ -49,3 +49,8 @@ unit: ^ {6}[ ]*COPY +([A-Z0-9]+)
 
 files: .*\.(jcl|JCL)
 unit: EXEC +PGM=([A-Z0-9]+)
+
+## Consolidate
+
+- cluster: calls, exec-pgm
+- context: copies

package/kits/mainframe-java/packs/cobol-springboot/prompts/consolidate.md

@@ -0,0 +1,8 @@
+In a COBOL estate a domain feature is a job's worth of business behaviour: the
+program a JCL step executes together with every program it CALLs and the
+copybooks they share, or a set of programs that post to the same ledger
+tables. Copybooks are context, never features of their own. Programs that
+only compute (fee, interest, limit) and are CALLed from several jobs belong to
+the feature that owns their business rule, not to every caller; say which in
+the evidence. Never join two batch jobs that touch different ledgers unless
+one executes the other.

package/kits/mainframe-java/packs/cobol-springboot/prompts/refine-propose.md

@@ -0,0 +1,10 @@
+The target is a Spring Boot service with JPA entities, a validation chain, and
+JUnit 5 acceptance tests over the seeded feature files. Things such a target
+usually PROVIDES, so a legacy program or scenario about them is a `provided`
+candidate once you have found the file that proves it: audit rows written by
+an aspect or entity listener, request logging, the transaction boundary a
+COBOL program opened and closed by hand, date and time stamping, and sequence
+allocation. Things commonly DEPRECATED in a COBOL estate, `drop` candidates
+when the source shows the evidence (a job step nothing schedules, a program no
+JCL executes and nothing CALLs, a report format the business retired): name
+the evidence, never guess from the program name alone. Never propose `defer`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llm4ts/shell",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Interactive shell and CLI for llm4ts: flow discovery, run-a-flow, and view",
   "license": "MIT",
   "type": "module",
@@ -23,6 +23,7 @@
     "./FlowCatalog": "./dist/FlowCatalog.js",
     "./FlowLaunch": "./dist/FlowLaunch.js",
     "./Menu": "./dist/Menu.js",
+    "./Refine": "./dist/Refine.js",
     "./Package": "./dist/Package.js",
     "./package.json": "./package.json"
   },
@@ -51,9 +52,9 @@
   "dependencies": {
     "@effect/platform-node": "4.0.0-rc.115",
     "@effect/platform-node-shared": "4.0.0-rc.115",
-    "@llm4ts/flow": "2.1.0",
-    "@llm4ts/runner": "2.1.0",
-    "@llm4ts/core": "2.1.0"
+    "@llm4ts/core": "2.2.0",
+    "@llm4ts/flow": "2.2.0",
+    "@llm4ts/runner": "2.2.0"
   },
   "peerDependencies": {
     "effect": "4.0.0-rc.115"

package/src/Cli.ts

@@ -1,4 +1,5 @@
 import { homedir } from "node:os"
+import { join, resolve } from "node:path"
 import { fileURLToPath } from "node:url"
 import * as Console from "effect/Console"
 import * as Effect from "effect/Effect"
@@ -18,6 +19,7 @@ import {
 } from "./FlowCatalog.ts"
 import { launchFlow } from "./FlowLaunch.ts"
 import { mainMenu } from "./Menu.ts"
+import { ModDir, refineSession } from "./Refine.ts"
 import { packageVersion } from "./Package.ts"
 
 export class ShellUsageError extends Schema.TaggedError<ShellUsageError>()("ShellUsage", {
@@ -295,6 +297,60 @@ const askCommand = Command.make(
     })
 ).pipe(Command.withDescription("Stream a one-shot prompt to the selected coding agent"))
 
+const refineCommand = Command.make(
+  "refine",
+  {
+    repo: Flag.String("repo").pipe(
+      Flag.optional,
+      Flag.withDescription(
+        "The LEGACY repository holding the extracted spec pack (defaults to the current directory)"
+      )
+    ),
+    pack: Flag.String("pack").pipe(
+      Flag.optional,
+      Flag.withDescription("Pack forwarded as LLM4TS_PACK, as for `llm4ts run`")
+    ),
+    target: Flag.String("target").pipe(
+      Flag.optional,
+      Flag.withDescription(
+        "The target repository, mounted read-only so the proposal can claim what it already provides (LLM4TS_TARGET_REPO)"
+      )
+    )
+  },
+  (config) =>
+    Effect.gen(function* () {
+      if (!process.stdin.isTTY || !process.stdout.isTTY) {
+        return yield* new ShellUsageError({
+          message:
+            "refine is interactive; off a terminal edit docs/modernization/decisions.md and run `llm4ts run modernize-refine`"
+        })
+      }
+      const repo = resolve(config.repo._tag === "Some" ? config.repo.value : process.cwd())
+      const flowPath = yield* resolveFlow("modernize-refine", shellTierPaths())
+      const environment: Record<string, string | undefined> = { ...process.env }
+      if (config.pack._tag === "Some") {
+        environment.LLM4TS_PACK = config.pack.value
+      }
+      if (config.target._tag === "Some") {
+        environment.LLM4TS_TARGET_REPO = resolve(config.target.value)
+      }
+      yield* refineSession({
+        modDir: join(repo, ModDir),
+        environment,
+        launch: (extra) =>
+          launchFlow({
+            flowPath,
+            taskArgs: ["--repo", repo],
+            environment: { ...environment, ...extra }
+          }).pipe(Effect.catch((error) => Console.error(error.message).pipe(Effect.as(1))))
+      })
+    })
+).pipe(
+  Command.withDescription(
+    "Interactively mark, deepen, and consolidate an extracted spec pack, then run modernize-refine on it (ADR 0015)"
+  )
+)
+
 const doctorCommand = Command.make("doctor", {}, () =>
   Effect.gen(function* () {
     const report = yield* makeDoctorProgram()
@@ -321,6 +377,7 @@ export const shellCommand = Command.make("llm4ts", {}, () =>
     kitsCommand,
     viewCommand,
     askCommand,
+    refineCommand,
     doctorCommand
   ])
 )