#!/usr/bin/env bash
# pi-crew pre-push hook — broaden the local release gate (D3).
#
# The 2026-10 CI-red recurrence: pushes to origin/main ran only
# test:critical (~120 tests) locally, while CI runs the FULL unit suite —
# three waves in a row shipped red. This hook closes that gap BEFORE the
# push leaves the machine.
#
# Scope:
#   push to refs/heads/main → check:conflict-markers + typecheck, then the
#                            FULL unit suite (npm run test:unit — the same
#                            gate CI runs); any failure blocks the push
#   any other ref          → fast gates only (check:conflict-markers +
#                            typecheck)
#
# Activated by `npm install` (prepare → scripts/install-hooks.mjs sets
# git config core.hooksPath .githooks) or manually:
#   git config core.hooksPath .githooks
# Emergency bypass:  git push --no-verify   (CI still gates main).

set -euo pipefail

cd "$(git rev-parse --show-toplevel)"

pushes_main=0
while read -r local_ref local_sha remote_ref remote_sha; do
	if [ "$remote_ref" = "refs/heads/main" ]; then
		pushes_main=1
	fi
done

if ! npm run check:conflict-markers; then
	echo "[pre-push] ✋ push blocked: conflict markers present."
	echo "[pre-push]    Fix: resolve the markers, or bypass with 'git push --no-verify' (CI still gates)."
	exit 1
fi
if ! npm run typecheck; then
	echo "[pre-push] ✋ push blocked: typecheck failed."
	echo "[pre-push]    Fix the errors above, or bypass with 'git push --no-verify' (CI still gates)."
	exit 1
fi

if [ "$pushes_main" = "1" ]; then
	echo "[pre-push] push to main: running the FULL unit suite (test:unit)…"
	# Capture the full log so a flake's failing test is identifiable even when
	# the push output is truncated by tooling (lesson 2026-10-07: three hook
	# blocks lost their failure detail to a trailing `| tail`).
	UNIT_LOG="${TMPDIR:-/tmp}/pi-crew-prepush-unit.log"
	if ! npm run test:unit 2>&1 | tee "$UNIT_LOG"; then
		echo "[pre-push] ✋ push blocked: test:unit failed (full log: $UNIT_LOG)."
		echo "[pre-push]    Fix the failures above, or bypass with 'git push --no-verify' (CI still gates)."
		exit 1
	fi

	# Pre-publish battery (2026-10-28, born from the v0.11.46/0.11.47
	# silent-worker incident): the LIVE real-Pi gate. One command, tiers
	# path-triggered from the diff (T1/T3/T11j always; T7 spawns a real
	# pi -p fast-fix smoke when spawn-affecting paths changed). Evidence lands
	# in .crew/audit/battery.jsonl. There is NO tier selection here on purpose —
	# a gate the agent may choose to skip is a gate that will be skipped.
	# No pi binary (CI-like hosts): PI_CREW_BATTERY_SKIP=1 records the skip in
	# the audit trail; a silent skip fails.
	echo "[pre-push] push to main: running the pre-publish battery (live real-Pi gate)…"
	if ! node scripts/pre-publish-battery.mjs; then
		echo "[pre-push] ✋ push blocked: pre-publish battery RED (see .crew/audit/battery.jsonl)."
		echo "[pre-push]    Gate KHÔNG CHẠY = KHÔNG PUBLISH — fix, or bypass with 'git push --no-verify' (CI still gates) and record WHY."
		exit 1
	fi
fi

echo "[pre-push] gates green."