69 lines
2.5 KiB
Markdown
69 lines
2.5 KiB
Markdown
# Row 162 live reads for the scratch-root plan (sage-0837, sage-0859)
|
|
|
|
One live read, at 2026-10-18T19:32:16Z, by Darkwing:
|
|
|
|
```
|
|
systemctl --user show [email protected] -p WorkingDirectory
|
|
```
|
|
|
|
Its output, as recorded in the session transcript:
|
|
|
|
```
|
|
WorkingDirectory=/home/jwoltje/.local/share/mosaic-stack/copies/52f35e7a0933e9fa845f59860a5de1709f9e5756
|
|
```
|
|
|
|
`systemctl show` reads the
|
|
unit's properties from the user manager. It writes nothing: no unit
|
|
file, no drop-in, no state under `~/.mosaic-dev` and no change to the
|
|
unit's state.
|
|
|
|
sage-0859 also allowed a read-only `systemctl --user is-active` on the
|
|
bus unit name. It was never called. The scratch data root has no store
|
|
file, so `plan_store` sets the store schema from the pointer before it
|
|
reaches the `is-active` branch.
|
|
|
|
The pointer's schema, `3f`, came from git in the canonical checkout, not
|
|
from anything live:
|
|
|
|
```
|
|
git show 52f35e7a0933e9fa845f59860a5de1709f9e5756:packages/bus/src/store.mjs
|
|
```
|
|
|
|
Nothing under `~/.mosaic-dev`, the live copies directory or the systemd
|
|
units was written. The scratch copy and its removal are in
|
|
`scratch-plan-steps.log`; the plan output is `scratch-plan.txt`.
|
|
|
|
## Rerun for target 8e7ea89a1 (sage-0871, mos-0810 D1-D2)
|
|
|
|
One more live read, at 2026-10-18T19:51:55Z, by Darkwing, at the start of
|
|
the sage-0871 slot:
|
|
|
|
```
|
|
systemctl --user show [email protected] -p WorkingDirectory
|
|
```
|
|
|
|
Its output:
|
|
|
|
```
|
|
WorkingDirectory=/home/jwoltje/.local/share/mosaic-stack/copies/52f35e7a0933e9fa845f59860a5de1709f9e5756
|
|
```
|
|
|
|
The live copy had not changed since the 19:32:16Z read. No `is-active`
|
|
read was made this time either. The pointer is hand-written as before:
|
|
copy `52f35e7a0`, schema `3f` from `git show` of that copy's store.mjs.
|
|
|
|
The script was `r1/plan-8e7.sh`, a copy of plan.sh with three changes:
|
|
the target is `8e7ea89a1` instead of `origin/refactor`, the scratch root
|
|
is `~/darkwing-scratch/r162/plan-8e7` and the output file is
|
|
`scratch-plan-8e7ea89a1.txt`. It ran from the r1 candidate worktree on
|
|
cfde62f9f, which matched `r1/candidate-manifest.sha256` at 19:51Z. The
|
|
scratch copy was made at 19:51:56Z and removed at 19:51:58Z, leaving 0
|
|
entries.
|
|
|
|
One defect in the step log: its "plan: written to" line names
|
|
`out/scratch-plan.txt`. My edit changed only the quoted output path, not
|
|
the unquoted one in that log line. The output went to
|
|
`out/scratch-plan-8e7ea89a1.txt`. The 606fafd43 output kept its sha256
|
|
(0586168e…), so the run did not touch it. The step log is kept as
|
|
written.
|