start-worklisted

# start-work · Step Zero Before Starting Work (Baseline First) Execute this workflow before touching **any content files** in this repository. Editing any files before completing baseline verification is strictly forbidden. ## Steps 1. Run `git fetch origin`. 2. Run `git status --short --branch` and `git log --oneline -3`: check the current branch, commit lag, and any uncommitted changes. 3. Dispatch according to the state table: | Current State | Action | |---|---| | Already on an **unmerged** `feature/*` branch | Proceed with work. If `origin/develop` has advanced, rebase only upon user confirmation. | | On `main` or any non-working branch (old or new) | **Never edit in place.** If there are uncommitted changes, save them with `git stash push -u`, then run `git switch -c feature/<topic> origin/develop`. Never blindly `stash pop` into a commit — replay changes against the fresh tree file by file. | | Sits on local `develop` | Follow the "Zero Local develop Changes" iron rule: do not edit or commit; derive a new branch from `origin/develop`. | 4. Report a one-line summary to the user: original branch / commit lag / newly derived feature branch name. ## Branch Rules Digest (Authoritative text in AGENTS.md §4) - All work branches derive from the **latest `origin/develop`**; local `develop` remains untouched. - Direct `commit` / `push` to `develop` is strictly forbidden; `develop` evolves exclusively through GitHub PR merges. - **One Branch, One PR, Merge and Discard**: N