Name the branches as the rename leaves them
This commit is contained in:
@@ -7,7 +7,7 @@ Guidance for LLM agents working in this repository. What each file in it is for
|
||||
|
||||
A ground-up TypeScript rewrite of `larvitsmpp` 0.4.0, published as `@larvit/smpp` 1.0.0. The branch
|
||||
started from an orphan commit — no history from 0.4.0 is carried over. The 0.4.0 source is still
|
||||
readable on the `master` branch of the same repository and is the reference for protocol behaviour,
|
||||
readable on the `v0.4.0` branch of the same repository and is the reference for protocol behaviour,
|
||||
not for structure or style.
|
||||
|
||||
## Goals
|
||||
|
||||
@@ -90,12 +90,12 @@ Then add the file to README.md's findings table.
|
||||
Every defect a phase records is fixed before the next phase runs — a fix can change behaviour in
|
||||
ways the next experiment must see. One fix per defect class, as its own change:
|
||||
|
||||
1. A worktree on a branch off `origin/typescript` (never `origin/master`, the 0.4.0 code), named
|
||||
1. A worktree on a branch off `origin/main` (never `origin/v0.4.0`, the 0.4.0 code), named
|
||||
for the defect.
|
||||
2. Regression tests in `test/` first, naming the behaviour with the reproducer from the findings;
|
||||
then the implementation; then the decision record in the root `AGENTS.md` where the fix settles
|
||||
a question of the wire or the session's life.
|
||||
3. `/larv-review` on the branch, with the pull request based on `typescript`. When it marks the PR
|
||||
3. `/larv-review` on the branch, with the pull request based on `main`. When it marks the PR
|
||||
ready, squash-merge it.
|
||||
4. Back in the experiments worktree: fast-forward `typescript`, rerun the experiment that found the
|
||||
4. Back in the experiments worktree: fast-forward `main`, rerun the experiment that found the
|
||||
defect, delete the workaround its test carried, and note the fix in the findings file.
|
||||
|
||||
Reference in New Issue
Block a user