fix(issue-format): accept tilde provenance fences

[stranske]

Summary

• accept the formatter-supported ~~~text form for canonical Original Issue provenance archives
• keep matching close fences exact and preserve the existing fail-closed behavior for malformed or wrong-language archives
• cover both Workflows and consumer-template validator copies with the same regression

This is the source-of-truth correction for the duplicate active findings on:

• chore: sync workflow templates Manager-Database#1581 (comment)
• chore: sync workflow templates trip-planner#1716 (comment)

The current generated candidate heads remain unmergeable. After this source fix merges, Maint 68 must refresh the same stable candidate PRs in place.

Validation

• python3 -m pytest -q tests/scripts/test_issue_format.py — 138 passed
• uv run --with pytest --with pydantic pytest -q tests/scripts/test_issue_formatter.py tests/scripts/test_issue_optimizer.py tests/scripts/test_issue_pr_context.py — 112 passed
• uv run --with pytest --with pydantic --with PyYAML pytest -q tests/workflows/test_agents_issue_optimizer_format_trigger.py tests/workflows/test_sync_manifest_delivery.py tests/scripts/test_validate_template_completeness.py tests/scripts/test_validate_template_sync.py — 62 passed
• python3 scripts/validate_template_completeness.py — passed
• python3 scripts/validate_template_sync.py — passed
• root/template issue_format.py copies are byte-identical
• git diff --check — passed

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 46 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5235af6f-bb29-42aa-b7fb-3c30ead5806c

📥 Commits

Reviewing files that changed from the base of the PR and between f2e01a6 and ca4e49e.

📒 Files selected for processing (3)

• .github/scripts/issue_format.py
• templates/consumer-repo/.github/scripts/issue_format.py
• tests/scripts/test_issue_format.py

---

_{Comment @coderabbitai help to get the list of available commands.}

[stranske]

@codex review

[stranske]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[agents-workflows-bot]

Workflow source detected

PR #3064 now has valid workflow source context (origin=review_followup).

No linked GitHub issue is required for this PR.

[stranske-keepalive]

Automated Status Summary

Head SHA: 4b51699
Latest Runs: ⏳ pending — Gate
Required contexts: summary
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job	Result	Logs
(no jobs reported)	⏳ pending	—

Coverage Overview

• Coverage history entries: 1

Coverage Trend

Metric	Value
Current	76.27%
Baseline	85.00%
Delta	-8.73%
Minimum	70.00%
Status	✅ Pass

Top Coverage Hotspots (lowest coverage)

File	Coverage	Missing
scripts/issue_dedup_smoke.py	0.0%	4
scripts/runner_lib/__main__.py	0.0%	3
scripts/validate_template_sync.py	0.0%	81
scripts/langchain/topic_splitter.py	19.1%	57
tools/codex_log_analyzer.py	19.6%	140
scripts/repo_review_round2_runner.py	25.1%	344
scripts/prune_agent_stubs.py	39.7%	26
scripts/repo_review_round1_runner.py	40.7%	133
tools/ensure_workflow_timeout_variables.py	42.1%	74
scripts/sync_label_docs.py	42.9%	64
tools/discover_model_catalog.py	44.8%	55
scripts/repo_review_backlog_scan.py	45.3%	116
scripts/repo_review_body_writer.py	46.5%	86
tools/codex_session_analyzer.py	47.9%	59
scripts/create_verifier_labels.py	48.3%	58

Low Coverage Files (<50.0%)

File	Coverage	Missing
scripts/issue_dedup_smoke.py	0.0%	4
scripts/runner_lib/__main__.py	0.0%	3
scripts/validate_template_sync.py	0.0%	81
scripts/langchain/topic_splitter.py	19.1%	57
tools/codex_log_analyzer.py	19.6%	140
scripts/repo_review_round2_runner.py	25.1%	344
scripts/prune_agent_stubs.py	39.7%	26
scripts/repo_review_round1_runner.py	40.7%	133
tools/ensure_workflow_timeout_variables.py	42.1%	74
scripts/sync_label_docs.py	42.9%	64
tools/discover_model_catalog.py	44.8%	55
scripts/repo_review_backlog_scan.py	45.3%	116
scripts/repo_review_body_writer.py	46.5%	86
tools/codex_session_analyzer.py	47.9%	59
scripts/create_verifier_labels.py	48.3%	58

Updated automatically; will refresh on subsequent CI/Docker completions.

---

Keepalive checklist

Scope

No scope information available

Tasks

• No tasks defined

Acceptance criteria

• No acceptance criteria defined

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: ca4e49e00e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".