wip-commit is beta software. Support is best effort, and there is no
response-time or resolution-time guarantee. A local candidate and a published
prerelease have the same beta support boundary.
The newest published beta is the only supported beta unless a release note says otherwise. A published stable version will define a separate support policy.
After the repository is public, use its issue tracker for reproducible bugs and its discussion area for usage questions, if discussions are enabled. Do not put secrets, private paths, repository names, file contents, commit messages, or credentials in a report.
For a security issue, follow SECURITY.md. Do not report a suspected vulnerability in a public issue.
Community participation follows CODE_OF_CONDUCT.md. Use
the repository host's private reporting form on the Security tab for a
confidential conduct report. Start the title with Code of Conduct:. Do not
put a conduct report in a public issue.
If you suspect that a command captured foreign content or changed the wrong ref:
- Stop further capture and landing work.
- Preserve the worktree, index, agent ref, JSON result, and recovery receipt.
- Run
wip doctorand record only redacted output. - Do not stash, reset, clean, force-update, or delete state.
- Report the
wipversion, operating system, Git version, command outcome, typed error code,ref_updated, andintent_state.
The project does not promise recovery from manual changes to its state files, uncoordinated Git index mutation, malicious same-user processes, or commands outside the trust boundary in THREAT-MODEL.md.