Workspace canon instructs every Night Shift session to append its findings here:
Append findings to /Dev/night-shift/IMPROVEMENTS.md (one dated section per run): what worked, what didn't, pattern gaps (→ fix in repo's CLAUDE.md), per-task signal.
The file has never been committed. git status reports it ?? — not gitignored, simply never added. It is the only untracked file in the repo.
What that means
- 32,772 bytes across 12 dated sections exist on exactly one machine.
- Every session that followed the rule wrote into local-only storage.
- No other session, no other machine, and nothing in CI can read a word of it.
- A fresh clone of this repo gets none of it.
The rule has been working. The channel has not.
Why it matters beyond tidiness
This file is named as a durability lever for Night Shift rejections — the mechanism by which "this task type produces noise" survives from one run to the next instead of being re-litigated every cycle. havardljohansen/dev-cockpit#301 proposes replacing strict-superset bundling with curated subsets, and its own decisive question is whether rejections are durable:
"If rejections aren't durable, a curated-subset rule is strictly more expensive than superset — same audit cost, every cycle, forever."
With this file untracked, they are not. That proposal is blocked on this.
It is also dev-cockpit#306 (canon mandates a channel that the cockpit-feedback rule effectively forbids) and finding F14 of the 2026-08 canon audit.
Content is safe to commit — scanned
Before suggesting this, I checked it against the same bar used for anything crossing from local state into a shared repo:
| check |
result |
secret-prefixed strings (shpat_, ghp_, xox*-, AKIA, ap_sk_ …) |
0 |
| email addresses |
0 |
| named individuals |
1 — "Zakhar", in an engineering context |
It is task-quality findings about Night Shift itself. Nothing client-identifying.
Suggested fix
git add IMPROVEMENTS.md and commit. One command, and the 12 sections of accumulated signal become readable by every session instead of one machine.
Worth deciding at the same time whether new entries should keep appending here, or whether the per-run signal belongs somewhere with more structure now that there are 12 sections of it. Either answer is fine — but the current state, where canon mandates writing to a file nobody else can read, is the one option that helps nobody.
Filed rather than fixed: this is your repo, and the commit is yours to make.
Workspace canon instructs every Night Shift session to append its findings here:
The file has never been committed.
git statusreports it??— not gitignored, simply never added. It is the only untracked file in the repo.What that means
The rule has been working. The channel has not.
Why it matters beyond tidiness
This file is named as a durability lever for Night Shift rejections — the mechanism by which "this task type produces noise" survives from one run to the next instead of being re-litigated every cycle.
havardljohansen/dev-cockpit#301proposes replacing strict-superset bundling with curated subsets, and its own decisive question is whether rejections are durable:With this file untracked, they are not. That proposal is blocked on this.
It is also
dev-cockpit#306(canon mandates a channel that the cockpit-feedback rule effectively forbids) and finding F14 of the 2026-08 canon audit.Content is safe to commit — scanned
Before suggesting this, I checked it against the same bar used for anything crossing from local state into a shared repo:
shpat_,ghp_,xox*-,AKIA,ap_sk_…)It is task-quality findings about Night Shift itself. Nothing client-identifying.
Suggested fix
git add IMPROVEMENTS.mdand commit. One command, and the 12 sections of accumulated signal become readable by every session instead of one machine.Worth deciding at the same time whether new entries should keep appending here, or whether the per-run signal belongs somewhere with more structure now that there are 12 sections of it. Either answer is fine — but the current state, where canon mandates writing to a file nobody else can read, is the one option that helps nobody.
Filed rather than fixed: this is your repo, and the commit is yours to make.