docs: rescan rebased documentation hierarchy
This commit is contained in:
@@ -22,7 +22,7 @@ Do not assume a path or branch name. DSH is usually installed from source with a
|
||||
|
||||
1. Create a fresh task branch and worktree from the recorded staging tip, using the repository-required worktree location — default to `.worktrees/` under the repository root unless the repository requires otherwise. Never implement or commit directly on staging.
|
||||
2. Implement the change, then select and run the repository-required review and checks. If a check fails, fix the cause and rerun it before integration.
|
||||
3. Test assembled TUI behavior interactively in a dedicated tmux session. Test other interactive UI behavior in a browser; unit tests and snapshots alone are insufficient.
|
||||
3. Test assembled interactive behavior in the Web UI; unit tests and snapshots alone are insufficient.
|
||||
4. Record the task tip and confirm the task worktree is clean before integration.
|
||||
|
||||
## Integrate under the lock
|
||||
|
||||
@@ -23,5 +23,5 @@ Classification and a recommendation are not publishing approval. Obtain explicit
|
||||
3. Review the outgoing commits and diff against upstream. Confirm they contain only the approved feature, no credentials or personal data, and a clean worktree.
|
||||
4. Reconfirm the approved feature name and publishing target before the first push. Do not infer authorization from earlier local work.
|
||||
5. Push only that branch and open only a draft PR. Keep its description synchronized with later changes.
|
||||
6. For a TUI feature, preferably attach a screenshot from the assembled application after removing credentials and personal data.
|
||||
6. For a Web UI feature, attach a screenshot or GIF from the assembled application after removing credentials and personal data.
|
||||
7. Report the upstream base and branch commits, commands and checks run, pushed branch, and draft PR URL.
|
||||
|
||||
Reference in New Issue
Block a user