push

Pre-push hygiene is automated by auditing diffs, appending context to HANDOFF.md, updating RESEARCH-LOG.md, and verifying run-card metadata before guiding the final commit workflow. This ensures every push is a deliberate, well-documented handoff capturing all necessary notes.

A pre-push governance workflow coordinates step verification, run-card YAML alignment, and interface checks before committing changes. It enforces documentation updates in HANDOFF and RESEARCH-LOG files to preserve traceability and capture rationale for future development sessions.

To capture context for future sessions, append decisions and rationale to HANDOFF.md and RESEARCH-LOG.md during the pre-push sequence. This handoff logging provides necessary continuity and documents dead ends alongside the committed code changes.

Yes, pre-push interface checks automatically flag changes touching onchain or interface files for review. This scope audit surfaces what needs attention by reviewing diffs and status before the commit workflow preserves traceability.

Aligning run-card YAML frontmatter status requires verifying and updating the metadata to match reality during the pre-push hygiene process. This run-card hygiene step ensures documentation updates accurately reflect the actual state of code contributions before committing.

You need to update a RESEARCH-LOG.md file during the pre-push workflow to record decisions, dead ends, and rationale. This research logging satisfies governance requirements by capturing the reasoning behind code changes before the final push sequence.