review: M5d-1 epochs and compaction
Co-Authored-By: Grok 4.6 <noreply@x.ai>
This commit is contained in:
@@ -96,6 +96,8 @@ These come from defects found in review. The evidence is in `docs/implementer-le
|
||||
does not match, look at `git diff <file>` for your own earlier edit, then stop and report; never
|
||||
anchor the edit on another line.
|
||||
- Write your log row from `git diff` after staging, naming only what the diff shows.
|
||||
- Add the log row immediately under the table header (newest first). Do not insert it by date
|
||||
among older rows.
|
||||
- After `gate: ok`, do not run `cargo test --workspace` only to count tests. If HEAD already has
|
||||
this task's commit and a `done` row, stop.
|
||||
|
||||
@@ -129,9 +131,10 @@ Useful while working: `cargo test -p <crate> --test <file>` runs one test file,
|
||||
|
||||
## The implementer log
|
||||
|
||||
Before you commit, add one row to the table in `docs/implementer-log.md` and include the file in
|
||||
the commit. Be honest: the log is how the owner judges the process, and a wrong row is worse than a
|
||||
bad one.
|
||||
Before you commit, add one row immediately under the header of the table in
|
||||
`docs/implementer-log.md` (newest first) and include the file in the commit. Do not insert the
|
||||
row by date among older rows. Be honest: the log is how the owner judges the process, and a wrong
|
||||
row is worse than a bad one.
|
||||
|
||||
| Column | What to write |
|
||||
|---|---|
|
||||
|
||||
Reference in New Issue
Block a user