18 lines
1.3 KiB
Markdown
18 lines
1.3 KiB
Markdown
# Integration Gate
|
|
|
|
Use this gate to promote completed task facts into canonical project memory.
|
|
|
|
## Requirements
|
|
|
|
- Run in an exclusively owned integration worktree.
|
|
- Hold the repository integration lock.
|
|
- Verify the task commits being integrated are present.
|
|
- Review source task records, task-prefixed supporting records, promotion candidates, and semantic conflicts in read-only mode.
|
|
- Write integration notes only to the integration task's own task record or `{task_id}__<slug>.md` supporting records.
|
|
- Ask before changing architecture direction, product behavior, or accepted decisions.
|
|
- Record source task or merge commits under `Integrated Through` in `current-state.md`.
|
|
- After a completed task is merged into the main branch, proactively ask whether to clean up its remaining worktree, naming the absolute path and branch. Follow the loaded skill's Post-Merge Cleanup procedure; merge permission alone does not authorize deletion.
|
|
- After explicit cleanup approval, retire only a clean, ready, managed linked worktree from another worktree. Require its committed task record to say `Ready for Integration`, and preserve its task branch and commit. A declined or pending cleanup leaves the completed merge valid.
|
|
|
|
Do not resolve meaningful document conflicts with `ours`, `theirs`, or union merge rules.
|