@haus-tech/haus-workflow 5.12.1 → 6.0.0

package/library/global/skills/request/scripts/svep.mjs

@@ -20,13 +20,15 @@
  * steg som ålägger startaren en skrivning måste peka ut vem som utför den.
  *
  * Användning:
- *   node svep.mjs --repo-rot <abs> --konto <namn> --modell <m> [--modell <m>]...
+ *   node svep.mjs --repo-rot <abs> [--arkiv <abs>] --konto <namn> --modell <m> [--modell <m>]...
  *                 --exp <experiments/<slug>> [--exp ...]...
  *                 [--tickets-parallellt 2] [--modeller-parallellt 4]
  *                 [--om | --hoppa-över] [--claude <kommando>]
  *
- * Ett relativt --exp löses mot <repo-rot>/.haus-workflow/requests/. Varje
- * experimentkatalog måste bära onskemal.md, kallmanifest.md och experiment.json
+ * Ett relativt --exp löses mot arkivroten: --arkiv när den ges (ARKIVROT: från
+ * `archive.mjs rot`), annars härledd ur --repo-rot:s git common dir, alltså
+ * <huvudutcheckning>/.haus-workflow/requests/ (ADR-0154, ADR-0155).
+ * Varje experimentkatalog måste bära onskemal.md, kallmanifest.md och experiment.json
  * med `ticket` (huvudkonversationen förbereder dem, utvärdera steg 1 till 3);
  * saknas något märks ticketen och hoppas över, svepet fortsätter.
  *
@@ -44,7 +46,7 @@ import { existsSync, readFileSync, writeFileSync, readdirSync, realpathSync } fr
 import { spawn, spawnSync } from 'node:child_process'
 import path from 'node:path'
 import { fileURLToPath } from 'node:url'
-import { canonicalModel, matcharModell, avgorDeps, schemalagg } from './lib.mjs'
+import { arkivRot, canonicalModel, matcharModell, avgorDeps, schemalagg } from './lib.mjs'
 
 // matcharModell, avgorDeps och schemalagg flyttade till lib.mjs (delade
 // byggstenar för requestmotorns kontrollscript); re-exporteras här så
@@ -68,6 +70,7 @@ const STANDARD_MODELLTAK = 4
 const SIGINT_EXIT = 130
 const VARDEFLAGGOR = [
   'repo-rot',
+  'arkiv',
   'konto',
   'modell',
   'exp',
@@ -78,7 +81,7 @@ const VARDEFLAGGOR = [
 const BOOLFLAGGOR = ['om', 'hoppa-över']
 
 export const ANVANDNING = [
-  'användning: svep.mjs --repo-rot <abs> --konto <namn> --modell <m> [--modell <m>]...',
+  'användning: svep.mjs --repo-rot <abs> [--arkiv <abs>] --konto <namn> --modell <m> [--modell <m>]...',
   '                     --exp <experiments/<slug>> [--exp ...]...',
   `                     [--tickets-parallellt ${STANDARD_TAK}] [--modeller-parallellt ${STANDARD_MODELLTAK}]`,
   '                     [--om | --hoppa-över] [--claude <kommando>]',
@@ -119,6 +122,8 @@ export function tolkaArgv(argv) {
   if (bool.om && bool['hoppa-över']) return { fel: '--om och --hoppa-över utesluter varandra' }
   if (!path.isAbsolute(enkla['repo-rot']))
     return { fel: `--repo-rot måste vara en absolut sökväg (fick "${enkla['repo-rot']}")` }
+  if (enkla.arkiv !== undefined && !path.isAbsolute(enkla.arkiv))
+    return { fel: `--arkiv måste vara en absolut sökväg (fick "${enkla.arkiv}")` }
   const dubbletter = listor.modell.filter((m, i) => listor.modell.indexOf(m) !== i)
   if (dubbletter.length > 0)
     return {
@@ -142,13 +147,22 @@ export function tolkaArgv(argv) {
     om: bool.om,
     hoppaOver: bool['hoppa-över'] || !bool.om,
     claude: enkla.claude ?? 'claude',
+    arkiv: enkla.arkiv ?? null,
   }
 }
 
 /** Ett relativt --exp är arkivrelativt (`experiments/<slug>`), som SKILL.md
- *  skriver det; ett absolut används som det är. */
-export function losExp(exp, repoRot) {
-  return path.isAbsolute(exp) ? exp : path.join(repoRot, '.haus-workflow', 'requests', exp)
+ *  skriver det, och löses mot arkivroten; ett absolut används som det är. */
+export function losExp(exp, arkiv) {
+  return path.isAbsolute(exp) ? exp : path.join(arkiv, exp)
+}
+
+/** Arkivroten när --arkiv saknas: huvudutcheckningens arkiv via git common
+ *  dir (ADR-0154), så en worktree som --repo-rot aldrig blir arkivets hem.
+ *  Utan git, eller med en common dir som inte heter .git, faller den
+ *  tillbaka på <repoRot>/.haus-workflow/requests. */
+export function losArkiv(repoRot) {
+  return arkivRot(repoRot)?.arkivRot ?? path.join(repoRot, '.haus-workflow', 'requests')
 }
 
 /** `default` som modellvärde ger katalognamnet `baseline/` (The experiment area: `experiments/`). */
@@ -305,10 +319,13 @@ export function sparrKataloger(dir) {
   return delar.length === 0 ? [dir] : delar.flatMap(sparrKataloger)
 }
 
+/** En USD-cell: `decimaler` decimaler, `-` när beloppet saknas. Delas med
+ *  bedom.mjs, som visar två decimaler där svepet visar fyra. */
+export const usd = (u, decimaler = 4) => (Number.isFinite(u) ? u.toFixed(decimaler) : '-')
+
 /** Sluttabellen: en rad per (ticket, modell). */
 export function renderaTabell(rader) {
   const wall = (ms) => (Number.isFinite(ms) ? `${ms}ms` : '-')
-  const usd = (u) => (Number.isFinite(u) ? u.toFixed(4) : '-')
   return [
     '| ticket | modell | körning | status | wall | USD |',
     '| --- | --- | --- | --- | --- | --- |',
@@ -330,7 +347,7 @@ const arkiv = (args, cwd) =>
 
 const felText = (r) => (r.stderr || r.stdout || '').trim() || `exit ${r.status}`
 
-const skrivMatning = (katalog, matning) =>
+export const skrivMatning = (katalog, matning) =>
   writeFileSync(path.join(katalog, 'matning.json'), JSON.stringify(matning, null, 2) + '\n')
 
 const lasKorningsrad = (expDir, nyckel) => {
@@ -346,8 +363,20 @@ const lasKorningsrad = (expDir, nyckel) => {
  *  runt den. korning.json skrivs av korning.mjs självt (filens ägare); här
  *  sparas bara stderr som stderr.log. matning.json skrivs ÄVEN när processen
  *  faller eller inte går att starta: en kraschad körning har en klocktid.
- *  `pagaende` är svepets register för Ctrl-C. */
-function korInre({ claude, gid, modell, katalog, expDir, repoRot, pagaende, nyckel }) {
+ *  `pagaende` är svepets register för Ctrl-C. `args` ersätter
+ *  experimentlägets argument (bedom.mjs skickar produktionslägets `--post`,
+ *  ADR-0155); utan `args` är anropet svepets som förut. */
+export function korInre({
+  claude,
+  gid,
+  modell,
+  katalog,
+  expDir,
+  repoRot,
+  pagaende,
+  nyckel,
+  args = null,
+}) {
   return new Promise((resolve) => {
     const startad = new Date()
     let stderr = ''
@@ -373,7 +402,7 @@ function korInre({ claude, gid, modell, katalog, expDir, repoRot, pagaende, nyck
     try {
       barn = spawn(
         process.execPath,
-        korningArgs({ katalog, expDir, repoRot, gid, modell, claude }),
+        args ?? korningArgs({ katalog, expDir, repoRot, gid, modell, claude }),
         {
           cwd: repoRot,
           stdio: ['ignore', 'pipe', 'pipe'],
@@ -695,7 +724,8 @@ async function main(argv) {
     process.exit(SIGINT_EXIT)
   })
 
-  const exps = val.exps.map((e) => losExp(e, val.repoRot))
+  const arkivrot = val.arkiv ?? losArkiv(val.repoRot)
+  const exps = val.exps.map((e) => losExp(e, arkivrot))
   const resultat = await schemalagg(exps, val.taket, (exp) => korTicket(exp, val, pagaende, ut))
 
   const rader = []

package/library/global/skills/request-assess-impact/SKILL.md

@@ -80,10 +80,7 @@ If the item comes back with the outcome `DELA_UPP`, it could not be bracketed ag
 
 The last point decides whether the split is worth anything. If all parts require the same manual walkthrough of the same flows in the same environments, the heaviest work is multiplied by the split instead of divided. In that case, write that out.
 
-**Two kinds of parts, and they end up in different places:**
-
-- If the part can be delivered on its own, it becomes a **separate request**, with its own spec and its own delivery. Write that, but do not write the spec: `request-write-spec` does that.
-- If it cannot be delivered on its own, it becomes a **part of the same item**, delivered together with the rest.
+**Every part becomes a subtask under the same item**, never a separate request, whether or not the part could be delivered on its own. Whether a part could be delivered on its own still matters for the order of the work: write it per part, since it says which part can ship first. It never changes where the part ends up.
 
 **The parts inherit the item's spec and this analysis.** Write no separate spec and no separate analysis per part. Each part gets a scope line that says which part of the spec it covers, and is scored against the shared source material. The customer ordered one thing; the split is internal structure.
 

package/library/global/skills/request-sync/SKILL.md

@@ -25,12 +25,16 @@ Read `.haus-workflow/request.json` in the repo root:
   "customer_board": "1202738613029434",
   "customer_section": "1202738613029441",
   "customer_section_name": "Mina sidor",
-  "collection_board": "1217668109816859"
+  "collection_board": "1217668109816859",
+  "design_mode": "interview",
+  "auto_sync_spec": true
 }
 ```
 
 `customer_section` is missing when the board is not divided into sections, and when the setup was run before the section step existed. `customer_section_name` exists only so it can be shown in confirmations: **always match on gid, never on name.**
 
+`design_mode` is `interview` (default, also when the key is absent) or `draft`. `draft` (ADR-0156) lets `/request bedöm` draft the design of an approved item that has none and have a second machine read it before the item is priced; the setup never asks for it, a human edits the file to opt in. `auto_sync_spec` (`true` by default, also when the key is absent): the request skill places a spec at 🔍 without a "go" unless it is `false` (ADR-0157); the setup writes the default and never asks for it, a human edits the file to opt out.
+
 **If the file is missing: run the setup below.** Never guess from the repo name or the folder name.
 
 If the file exists: **verify the board once, before the first write.** Look up `customer_board` by gid and print the name: _"Writing to Vafab Mina sidor, is that right?"_ Putting a customer's request on the wrong customer board is the only error in the entire flow that another customer can see, and it cannot be cleaned up quietly.
@@ -77,7 +81,9 @@ Fetch the fields on both boards and go through three things:
   "customer_board": "1217634399775198",
   "customer_section": "1217634399775205",
   "customer_section_name": "Mina sidor",
-  "collection_board": "1217668109816859"
+  "collection_board": "1217668109816859",
+  "design_mode": "interview",
+  "auto_sync_spec": true
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haus-tech/haus-workflow",
-  "version": "5.12.1",
+  "version": "6.0.0",
   "description": "Haus AI workflow CLI for Claude Code.",
   "type": "module",
   "bin": {