@@ -18,6 +18,10 @@ Hard limits:
1818- Do not force GIFs for internal-only, workflow-only, test-only, docs-only, or
1919 otherwise non-visual PRs. A no-visual-proof manifest is a successful workflow
2020 outcome when GIFs would be misleading, but it is not proof that the PR passed.
21+- Do not skip Telegram-visible PRs just because the proof needs a specific
22+ message, mock response, media attachment, command, button, reaction, stop
23+ timing, approval prompt, or progress/final delivery sequence. First write a
24+ concrete proof plan and try the standard harness path.
2125- Keep public-facing manifest summaries short and user-domain. Do not mention
2226 harness internals, mock-provider limits, secret/trust boundaries, local paths,
2327 transcript seeding, or workflow implementation details in the summary.
@@ -42,7 +46,15 @@ Required workflow:
42462. Inspect the PR with `gh pr view "$MANTIS_PR_NUMBER"` and
4347`gh pr diff "$MANTIS_PR_NUMBER"`.
44483. Decide whether the PR has a visibly reproducible Telegram Desktop
45- before/after. If it does not, write
49+ before/after. Treat these as visible until proven otherwise: message text
50+ formatting/content, progress drafts, native drafts, final delivery, media or
51+ document delivery, inline buttons, approval prompts, stop/abort behavior,
52+ reactions/status indicators, guest/inline responses, TTS/voice/audio
53+ delivery, and routing changes whose result is visible in the chat. For those
54+ PRs, define the exact Telegram stimulus and expected main/PR visual delta
55+ before deciding to skip.
56+57+ If the PR does not have a Telegram-visible before/after, write
4658`${MANTIS_OUTPUT_DIR}/mantis-evidence.json` with `comparison.pass: true`, no
4759 artifacts, and a summary that starts with
4860`Mantis did not generate before/after GIFs because`. Include a short
@@ -78,8 +90,9 @@ than Telegram-visible behavior`. Use this manifest shape and do not create
7890```
79918092 If the PR appears visual but proof is blocked by Telegram Desktop session
81- state, authorization, credentials, Crabbox, or another capture-infrastructure
82- issue, do not describe it as a no-visual PR. Write a manifest with
93+ state, authorization, credentials, Crabbox, missing Telegram client support,
94+ unavailable media/provider setup, or another capture-infrastructure issue,
95+ do not describe it as a no-visual PR. Write a manifest with
8396`comparison.pass: false`, skipped lanes, no artifacts, and a summary that
8497 starts with `Mantis could not capture Telegram Desktop proof because`. The
8598 publisher will keep that out of PR comments so the failure stays in the
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。