[E00-S01-T07] pnpm 11.23.0 workspace committed #160

New Issue

Closed

opened 2026-08-27 00:06:34 +00:00 by kpcto · 8 comments

kpcto commented 2026-08-27 00:06:34 +00:00

Owner

Copy Link

Copy Source

Parent story: [E00-S01] Workspace bootstrap (#58)

Intent

Pin and commit the pnpm 11.23.0 workspace configuration.

Acceptance criteria

• pnpm 11.23.0 workspace is committed
• install uses the committed pnpm version

Explicitly out of scope

• Node engine restriction (E00-S01-T08)
• TypeScript exact dependency (E00-S01-T09)
• strict base tsconfig (E00-S01-T10)

Test plan

• clean pnpm install --frozen-lockfile succeeds

Rollback note

• revert the pnpm/packageManager configuration

Owning stream

platform

Risk quadrant

agent-full

> Parent story: [E00-S01] Workspace bootstrap (#58) ## Intent Pin and commit the pnpm 11.23.0 workspace configuration. ## Acceptance criteria - pnpm 11.23.0 workspace is committed - install uses the committed pnpm version ## Explicitly out of scope - Node engine restriction (E00-S01-T08) - TypeScript exact dependency (E00-S01-T09) - strict base tsconfig (E00-S01-T10) ## Test plan - clean `pnpm install --frozen-lockfile` succeeds ## Rollback note - revert the pnpm/packageManager configuration ### Owning stream platform ### Risk quadrant agent-full

kpcto added this to the Sprint 0 milestone 2026-08-27 00:06:34 +00:00

kpcto added the

status

ready

kind

task

labels 2026-08-27 00:06:34 +00:00

bot-dispatcher added

status

proposed

and removed

status

ready

kind

task

labels 2026-08-27 00:06:35 +00:00

bot-dispatcher commented 2026-08-27 00:06:35 +00:00

Member

Copy Link

Copy Source

Auto-reverted by dispatcher: DoR lint: required section "Intent" is empty; required section "Acceptance criteria" is empty; required section "Explicitly out of scope" is empty; required section "Test plan" is empty; required section "Rollback note" is empty; acceptance criteria: no bullet assertions found

status/ready may only be applied by a human maintainer.

> Auto-reverted by dispatcher: DoR lint: required section "Intent" is empty; required section "Acceptance criteria" is empty; required section "Explicitly out of scope" is empty; required section "Test plan" is empty; required section "Rollback note" is empty; acceptance criteria: no bullet assertions found `status/ready` may only be applied by a human maintainer.

kpcto added the

kind

task

label 2026-08-27 21:23:37 +00:00

kpcto added

status

ready

and removed

status

proposed

labels 2026-08-28 08:59:10 +00:00

bot-dispatcher added

loop

1

status

in-progress

and removed

status

ready

labels 2026-08-28 08:59:10 +00:00

bot-dispatcher commented 2026-08-28 08:59:11 +00:00

Member

Copy Link

Copy Source

agent: dispatcher
phase: complete
plan_summary: Dispatch #160: [E00-S01-T07] pnpm 11.23.0 workspace committed (platform)

```yaml agent: dispatcher phase: complete plan_summary: Dispatch #160: [E00-S01-T07] pnpm 11.23.0 workspace committed (platform) ```

bot-implementer commented 2026-08-28 09:02:54 +00:00

Member

Copy Link

Copy Source

agent: implementer
issue: 160
phase: started
branch: feature/160
objective: "[E00-S01-T07] pnpm 11.23.0 workspace committed"
acceptance:
  - pnpm 11.23.0 workspace is committed
  - install uses the committed pnpm version
constraints:
  - out of scope: Node engine restriction (E00-S01-T08)
  - out of scope: TypeScript exact dependency (E00-S01-T09)
  - out of scope: strict base tsconfig (E00-S01-T10)
plan:
  - verify committed workspace state (packageManager pin, workspace yaml, lockfile, CI corepack wiring)
  - add criterion -> test regression suite (tests/workspace-config.test.mjs)
  - verify clean frozen-lockfile install uses pnpm 11.23.0
  - open PR from feature/160 with criterion -> test table; wait for green CI
status: in-progress

```yaml agent: implementer issue: 160 phase: started branch: feature/160 objective: "[E00-S01-T07] pnpm 11.23.0 workspace committed" acceptance: - pnpm 11.23.0 workspace is committed - install uses the committed pnpm version constraints: - out of scope: Node engine restriction (E00-S01-T08) - out of scope: TypeScript exact dependency (E00-S01-T09) - out of scope: strict base tsconfig (E00-S01-T10) plan: - verify committed workspace state (packageManager pin, workspace yaml, lockfile, CI corepack wiring) - add criterion -> test regression suite (tests/workspace-config.test.mjs) - verify clean frozen-lockfile install uses pnpm 11.23.0 - open PR from feature/160 with criterion -> test table; wait for green CI status: in-progress ```

bot-implementer referenced this issue 2026-08-28 09:04:02 +00:00

[E00-S01-T07] Commit and lock in pnpm 11.23.0 workspace #374

bot-implementer commented 2026-08-28 09:05:07 +00:00

Member

Copy Link

Copy Source

agent: implementer
issue: 160
phase: complete
pr: 374
branch: feature/160
objective: "[E00-S01-T07] pnpm 11.23.0 workspace committed"
acceptance:
  - criterion: pnpm 11.23.0 workspace is committed
    result: pass
    evidence: >
      Workspace config committed and locked in by new regression suite
      tests/workspace-config.test.mjs (root package.json pins
      "packageManager": "pnpm@11.23.0"; pnpm-workspace.yaml declares
      apps/*, packages/*, extensions/*; pnpm-lock.yaml committed with
      lockfile version 9.0 and an importer for every workspace package).
      Mutation-probed: pin -> pnpm@11.22.0 makes the tests fail.
  - criterion: install uses the committed pnpm version
    result: pass
    evidence: >
      `corepack pnpm --version` resolves 11.23.0 (asserted by test);
      clean-state `pnpm install --frozen-lockfile` succeeds "using pnpm
      v11.23.0"; CI workflow enables corepack and installs frozen.
method:
  - verified committed workspace state from T01 (pin, workspace yaml, lockfile, CI wiring)
  - added tests/workspace-config.test.mjs (6 tests, node:test, zero deps)
  - clean frozen-lockfile install from branch head -> exit 0, pnpm v11.23.0
  - pnpm test -> 16/16 pass (10 existing + 6 new)
  - mutation probe: pin change to 11.22.0 fails 2 tests; restored -> 16/16
  - opened PR #374 from feature/160 with criterion -> test table
ci:
  run: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45
  job: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45/jobs/57
  conclusion: success (CI / Frozen lockfile install, pull_request @ 23a574d)
notes: >
  No out-of-scope discoveries. E00-S01-T08/T09/T10 untouched. CI pipeline
  wiring of the test suite remains E00-S05 by design (CI workflow file
  untouched, consistent with T05/T06).
status: done

```yaml agent: implementer issue: 160 phase: complete pr: 374 branch: feature/160 objective: "[E00-S01-T07] pnpm 11.23.0 workspace committed" acceptance: - criterion: pnpm 11.23.0 workspace is committed result: pass evidence: > Workspace config committed and locked in by new regression suite tests/workspace-config.test.mjs (root package.json pins "packageManager": "pnpm@11.23.0"; pnpm-workspace.yaml declares apps/*, packages/*, extensions/*; pnpm-lock.yaml committed with lockfile version 9.0 and an importer for every workspace package). Mutation-probed: pin -> pnpm@11.22.0 makes the tests fail. - criterion: install uses the committed pnpm version result: pass evidence: > `corepack pnpm --version` resolves 11.23.0 (asserted by test); clean-state `pnpm install --frozen-lockfile` succeeds "using pnpm v11.23.0"; CI workflow enables corepack and installs frozen. method: - verified committed workspace state from T01 (pin, workspace yaml, lockfile, CI wiring) - added tests/workspace-config.test.mjs (6 tests, node:test, zero deps) - clean frozen-lockfile install from branch head -> exit 0, pnpm v11.23.0 - pnpm test -> 16/16 pass (10 existing + 6 new) - mutation probe: pin change to 11.22.0 fails 2 tests; restored -> 16/16 - opened PR #374 from feature/160 with criterion -> test table ci: run: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45 job: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45/jobs/57 conclusion: success (CI / Frozen lockfile install, pull_request @ 23a574d) notes: > No out-of-scope discoveries. E00-S01-T08/T09/T10 untouched. CI pipeline wiring of the test suite remains E00-S05 by design (CI workflow file untouched, consistent with T05/T06). status: done ```

bot-reviewer commented 2026-08-28 09:05:33 +00:00

Member

Copy Link

Copy Source

agent: reviewer
verdict: approve

```yaml agent: reviewer verdict: approve ```

bot-dispatcher added

status

review

and removed

status

in-progress

loop

1

kind

task

labels 2026-08-28 09:05:34 +00:00

bot-reviewer commented 2026-08-28 09:05:39 +00:00

Member

Copy Link

Copy Source

agent: reviewer
verdict: approve
findings: []

```yaml agent: reviewer verdict: approve findings: [] ```

kpcto closed this issue 2026-08-28 09:07:37 +00:00

kpcto added

kind

task

status

done

and removed

status

review

labels 2026-08-28 09:07:37 +00:00

bot-tester commented 2026-08-28 09:07:58 +00:00

Member

Copy Link

Copy Source

agent: tester
issue: 160
phase: started
pr: 374
objective: "independently probe PR #374 for #160 (pnpm 11.23.0 workspace committed)"
acceptance:
  - pnpm 11.23.0 workspace is committed
  - install uses the committed pnpm version
constraints:
  - never edit the implementer's tests in the same PR
method:
  - checkout feature/160 @ 23a574d (PR head, matches base main @ bd8c949)
  - inspect committed workspace config: package.json, pnpm-workspace.yaml, pnpm-lock.yaml, .gitea/workflows/ci.yml
  - run new suite: node --test tests/workspace-config.test.mjs
  - run full suite: node --test "tests/**/*.test.mjs"
  - clean-state install: corepack pnpm install --frozen-lockfile (no node_modules)
  - mutation probe: drift packageManager to pnpm@11.22.0, confirm tests fail, restore
status: in-progress

```yaml agent: tester issue: 160 phase: started pr: 374 objective: "independently probe PR #374 for #160 (pnpm 11.23.0 workspace committed)" acceptance: - pnpm 11.23.0 workspace is committed - install uses the committed pnpm version constraints: - never edit the implementer's tests in the same PR method: - checkout feature/160 @ 23a574d (PR head, matches base main @ bd8c949) - inspect committed workspace config: package.json, pnpm-workspace.yaml, pnpm-lock.yaml, .gitea/workflows/ci.yml - run new suite: node --test tests/workspace-config.test.mjs - run full suite: node --test "tests/**/*.test.mjs" - clean-state install: corepack pnpm install --frozen-lockfile (no node_modules) - mutation probe: drift packageManager to pnpm@11.22.0, confirm tests fail, restore status: in-progress ```

bot-tester commented 2026-08-28 09:08:09 +00:00

Member

Copy Link

Copy Source

agent: tester
issue: 160
phase: complete
pr: 374
verdict: pass
objective: "independently probe PR #374 for #160 (pnpm 11.23.0 workspace committed)"
acceptance:
  - criterion: pnpm 11.23.0 workspace is committed
    result: pass
    evidence: >
      Verified on branch feature/160 @ 23a574d. root package.json pins
      "packageManager": "pnpm@11.23.0"; pnpm-workspace.yaml declares
      apps/*, packages/*, extensions/*; pnpm-lock.yaml committed with
      "lockfileVersion: '9.0'" and importers for ".", apps/server,
      packages/core, extensions/example. The new suite
      tests/workspace-config.test.mjs (6 tests) passes and the assertions
      are non-vacuous: drifting packageManager to pnpm@11.22.0 makes
      tests 1 and 5 fail (pin assertion + corepack resolution).
  - criterion: install uses the committed pnpm version
    result: pass
    evidence: >
      `corepack pnpm --version` resolves 11.23.0 (exit 0). Clean-state
      install with no node_modules via `corepack pnpm install
      --frozen-lockfile` succeeds, reports "using pnpm v11.23.0", and
      leaves pnpm-lock.yaml byte-for-byte unchanged (git status clean).
      .gitea/workflows/ci.yml runs `corepack enable` then
      `pnpm install --frozen-lockfile`.
method:
  - checkout feature/160 @ 23a574d; confirmed PR head == base main @ bd8c949 + 1 commit (tests/workspace-config.test.mjs, +86/-0)
  - node --test tests/workspace-config.test.mjs -> 6/6 pass, exit 0
  - node --test "tests/**/*.test.mjs" -> 16/16 pass (10 existing + 6 new), exit 0
  - corepack pnpm --version -> 11.23.0 (exit 0)
  - clean corepack pnpm install --frozen-lockfile -> exit 0, "Done in 4.8s using pnpm v11.23.0", lockfile unchanged
  - mutation probe: packageManager -> pnpm@11.22.0 -> tests 1 & 5 fail (not ok); restored -> clean, 16/16
  - no files edited in the PR branch (working tree restored to clean)
ci:
  run: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45
  job: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45/jobs/57
  conclusion: success (CI / Frozen lockfile install, pull_request @ 23a574d; all 5 steps green)
findings: []
notes: >
  Independent run reproduces the implementer's claims (16/16, frozen
  install on pnpm 11.23.0, mutation probe). No out-of-scope drift into
  E00-S01-T08/T09/T10 detected. No edits made to the implementer's tests.
status: done

```yaml agent: tester issue: 160 phase: complete pr: 374 verdict: pass objective: "independently probe PR #374 for #160 (pnpm 11.23.0 workspace committed)" acceptance: - criterion: pnpm 11.23.0 workspace is committed result: pass evidence: > Verified on branch feature/160 @ 23a574d. root package.json pins "packageManager": "pnpm@11.23.0"; pnpm-workspace.yaml declares apps/*, packages/*, extensions/*; pnpm-lock.yaml committed with "lockfileVersion: '9.0'" and importers for ".", apps/server, packages/core, extensions/example. The new suite tests/workspace-config.test.mjs (6 tests) passes and the assertions are non-vacuous: drifting packageManager to pnpm@11.22.0 makes tests 1 and 5 fail (pin assertion + corepack resolution). - criterion: install uses the committed pnpm version result: pass evidence: > `corepack pnpm --version` resolves 11.23.0 (exit 0). Clean-state install with no node_modules via `corepack pnpm install --frozen-lockfile` succeeds, reports "using pnpm v11.23.0", and leaves pnpm-lock.yaml byte-for-byte unchanged (git status clean). .gitea/workflows/ci.yml runs `corepack enable` then `pnpm install --frozen-lockfile`. method: - checkout feature/160 @ 23a574d; confirmed PR head == base main @ bd8c949 + 1 commit (tests/workspace-config.test.mjs, +86/-0) - node --test tests/workspace-config.test.mjs -> 6/6 pass, exit 0 - node --test "tests/**/*.test.mjs" -> 16/16 pass (10 existing + 6 new), exit 0 - corepack pnpm --version -> 11.23.0 (exit 0) - clean corepack pnpm install --frozen-lockfile -> exit 0, "Done in 4.8s using pnpm v11.23.0", lockfile unchanged - mutation probe: packageManager -> pnpm@11.22.0 -> tests 1 & 5 fail (not ok); restored -> clean, 16/16 - no files edited in the PR branch (working tree restored to clean) ci: run: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45 job: http://gitea:3000/Fabrika/PersonalBlog/actions/runs/45/jobs/57 conclusion: success (CI / Frozen lockfile install, pull_request @ 23a574d; all 5 steps green) findings: [] notes: > Independent run reproduces the implementer's claims (16/16, frozen install on pnpm 11.23.0, mutation probe). No out-of-scope drift into E00-S01-T08/T09/T10 detected. No edits made to the implementer's tests. status: done ```

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

No results found.

Labels

Clear labels

agent/analyst-drafted

agent/analyst-drafted

kind

bug

kind

bug

kind

epic

kind

epic

kind

initiative

EPPP programme initiative

kind

story

kind

story

kind

task

EPPP engineering card/task decomposed from a story

kind

toil

kind

toil

loop

1

loop

1

loop

2

loop

2

loop

3

loop

3

needs/human-decision

needs/human-decision

needs/security-review

needs/security-review

risk

agent-full

risk

agent-full

risk

human-gated

risk

human-gated

risk

human-only

risk

human-only

size

l

size

l

size

m

size

m

size

s

size

s

status

blocked

status

blocked

status

done

Workflow: Done

status

in-progress

status

in-progress

status

proposed

status

proposed

status

ready

status

ready

status

review

status

review

stream

checkout

stream

checkout

stream

onboarding

stream

onboarding

stream

platform

stream

platform

tier/t0

trivial — implementer only, auto-merge

tier/t1

standard — implementer + reviewer + tester

tier/t2

complex — security if triggered, human merge

tier/t3

critical — full chain + security, human merge

No labels

kind

task

status

done

Milestone

No items

No Milestone Sprint 0

Projects

Clear projects

No projects

Assignees

Clear assignees

bot-analyst bot-dispatcher bot-implementer bot-migrations bot-reviewer bot-security bot-tester kpcto

No Assignees

5 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Fabrika/PersonalBlog#160