Repository navigation

fix: resolve status thresholds from the recorded session model #158

	name: Harness coverage advisory
Check warning on line 1 in .github/workflows/harness-coverage-check.yml View workflow run for this annotation GitHub Actions / Harness coverage advisory Workflow execution policy warning (evaluate mode) On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target

	on:
	pull_request_target:
	types: [opened, edited, reopened, synchronize, ready_for_review]

	concurrency:
	group: harness-coverage-${{ github.event.pull_request.number }}
	cancel-in-progress: true

	jobs:
	harness-coverage:
	runs-on: ubuntu-latest
	timeout-minutes: 5
	permissions:
	contents: read
	pull-requests: write
	issues: write
	steps:
	# Only the trusted base checkout runs. Under pull_request_target the job's own
	# token gets the write permissions declared above even for fork PRs, so the
	# advisory comment needs no App key; that key stays private-repo only.
	- uses: actions/checkout@v5
	- uses: actions/setup-node@v5
	with:
	node-version: "24"
	- name: Check conventional harness twins
	continue-on-error: true
	run: node scripts/harness-coverage-check.mjs
	env:
	GITHUB_TOKEN: ${{ github.token }}