feat(claude): WSP local build memory, and structural terseness rules for the Soviet Engineer style #90

2026-08-13T13:29:48+01:00

lyrathorpe commented

2026-08-13 13:29:48 +01:00

Two unrelated Claude config changes, split into a commit each.

Local build and test memory

A new memory recording how to compile and test core-services-cloud on this machine. The repo documents its own commands but assumes Windows and PowerShell, so this captures only the deltas:

dotnet comes from nixpkgs rather than the ambient PATH
artifactory credentials live in ~/.artifactoryenv and must be sourced per command, because shell state does not persist between tool calls
a curl check that separates an auth failure from a code failure, since a rejected token surfaces as NU1301: Unable to load the service index, which reads like a network fault
two Docker Desktop leftovers that break the component test environment: a dangling /usr/bin/docker symlink that shadows the working docker inside pwsh, and a credsStore pointing at a helper that does not exist, which makes docker login report success while storing nothing
component test canaries must be registered in the unleash mock, or SetFeatureFlag marks the test inconclusive rather than failing

Terseness rules in the output style

The style asked for terseness in tonal terms only. A dry register wrapped in headers, tables and a full status recap every turn passed its self-check while being exactly the verbose output the style exists to prevent.

Adds explicit limits — a default length ceiling, headers only for four or more items, report the delta rather than the accumulated state, state a caveat once — and replaces the self-check with one that tests length and form rather than tone.

nix flake check passes.

Two unrelated Claude config changes, split into a commit each. ## Local build and test memory A new memory recording how to compile and test `core-services-cloud` on this machine. The repo documents its own commands but assumes Windows and PowerShell, so this captures only the deltas: - dotnet comes from nixpkgs rather than the ambient PATH - artifactory credentials live in `~/.artifactoryenv` and must be sourced per command, because shell state does not persist between tool calls - a curl check that separates an auth failure from a code failure, since a rejected token surfaces as `NU1301: Unable to load the service index`, which reads like a network fault - two Docker Desktop leftovers that break the component test environment: a dangling `/usr/bin/docker` symlink that shadows the working docker inside pwsh, and a `credsStore` pointing at a helper that does not exist, which makes `docker login` report success while storing nothing - component test canaries must be registered in the unleash mock, or `SetFeatureFlag` marks the test inconclusive rather than failing ## Terseness rules in the output style The style asked for terseness in tonal terms only. A dry register wrapped in headers, tables and a full status recap every turn passed its self-check while being exactly the verbose output the style exists to prevent. Adds explicit limits — a default length ceiling, headers only for four or more items, report the delta rather than the accumulated state, state a caveat once — and replaces the self-check with one that tests length and form rather than tone. `nix flake check` passes.

lyrathorpe added 2 commits 2026-08-13 13:29:48 +01:00

docs(claude): record how to build and test core-services-cloud locally 4d6ad47837

The repo documents its own build and test commands, but assumes Windows and
PowerShell. This captures only the deltas that make them run on this machine:
dotnet from nixpkgs, artifactory credentials sourced per command because shell
state does not persist between tool calls, and a curl check that distinguishes
an auth failure from a code failure, since a rejected token surfaces as a
NuGet error that reads like a network fault.

Also records the two Docker Desktop leftovers that break the component test
environment, and the unleash registration a component test canary needs.

fix(claude): make the Soviet Engineer style enforce terseness structurally

CI / flake (push) Skipped

CI / flake (pull_request) Successful in 1m16s

Details

7041dfebfa

The style asked for terseness in tonal terms only, so a dry register wrapped in
headers, tables and a full status recap each turn passed its self-check while
being exactly the verbose output the style exists to prevent.

Add explicit limits: a default length ceiling, headers only for four or more
items, report the delta rather than the accumulated state, and state a caveat
once. Replace the self-check with one that tests length and form rather than
tone.

lyrathorpe merged commit c5b41ba6fd into main

2026-08-13 13:59:38 +01:00

lyrathorpe deleted branch feat/claude-wsp-build-memory-and-terseness

2026-08-13 13:59:38 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lyrathorpe/nixfiles#90