amsd-pipeline-shared 0.5.44 → 0.5.45

package/orchestrations/scripts/spec-mode-runner.js

@@ -4175,6 +4175,16 @@ PROPOSE TWO CLASSES OF AGENT.
 IMPLEMENTERS (kind: "implementer") author code, as described above. One roster of them spans
 every codeline.
 
+THE CODELINE'S STANDING ENGINEER, NOT A SPECIALITY. Propose ONE implementer per codeline that
+needs work written, named for that codeline (its engineer) and briefed on its WHOLE stack: its
+layout, build, conventions, tests and how to verify there. Any story on that codeline — a
+component change, a page, an integration, a localisation fix — must find this role fit to
+assign. Where codelines share one stack and structure, one engineer may cover them all, named
+for what they share. Propose a speciality (a narrower role) only where a codeline's structure
+genuinely splits it — a separate build, a separate deployable, a separately-owned subtree — and
+never for the kind of work one ticket happens to need: this roster outlives every ticket, and a
+roster of specialities leaves the next story with no one to assign.
+
 Every proposal states a "codeline". An implementer spans the project and uses "*". An
 investigator names the ONE codeline it reads, exactly as spelled in scope above. There is no
 third option and no omitting it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "amsd-pipeline-shared",
-  "version": "0.5.44",
+  "version": "0.5.45",
   "description": "The AMSD pipeline's shared components, one source for the bash pipeline and its Claude workflows: the model-call gateway (llm-handler.sh — retry, ladder, self-heal, cost) and the libraries it runs.",
   "license": "UNLICENSED",
   "bin": {