mempalace core 3.7.1 records neither which machine nor which harness produced a
drawer, and the single shared bearer token means the server cannot distinguish
clients. Today both facts survive only incidentally -- device in the per-device
inbox path, harness in the pi_*.jsonl filename -- so attribution for anything
filed outside the feeder has to be inferred after the fact.
Defaulting --agent to pi@$MEMPALACE_PI_DEVICE records both explicitly in a field
that already flows through to drawer metadata (added_by), for every enrolled
device, with no core change. Falls back to $USER, which is what pre-existing
drawers carry (added_by=joakim on fed transcripts, hence the ambiguity).
Not pushed: lands on machines at the next image build.
joakimp
c64ffa1d93