PR opened/synchronize/reopened triggers не включают edited. После invalid title rename прежний green commits остаётся; README обещает title check. Это metadata-policy gap P3, не runtime incident.
Expected Behavior
Changed PR title получает свежий commits proof без повторного Chromium/build/security pipeline на metadata-only event.
Evidence
Audit date 2026-10-11; 11, VERIFY-002 (frontend). Revision c8821200ce699dab1ce65360d1968d5877a2e78b; Confidence High static config; Verification status static/server behavior unverified.
Affected: .gitea/workflows/verify.yml:3–37; README:116–120. Root commits.yml edited precedent существует; сервер 1.27.3.
Scope
In scope
Existing metadata event/title job и required contexts verification.
Out of scope
Full pipeline на edited, новый event classifier, отключение required checks.
Proposed Approach
Selective commits execution; skipped downstream jobs не должны обходить failed required proof. Сверить actual Gitea protection/status behavior.
Acceptance Criteria
Invalid title-only rename обновляет commits в FAIL, valid rename — PASS на том же HEAD.
Metadata-only event не запускает app verify/build/Chromium.
Existing required contexts достижимы; normal code PR по-прежнему проходит полный pipeline.
Verification
Disposable PR title changes и read-only protection/status inspection; workflow syntax review. Не запускать full project verify ради YAML, если app inputs unchanged.
<!-- wealthledger-audit:2026-10-11:pr-title-edited-frontend -->
## Problem
PR opened/synchronize/reopened triggers не включают edited. После invalid title rename прежний green commits остаётся; README обещает title check. Это metadata-policy gap P3, не runtime incident.
## Expected Behavior
Changed PR title получает свежий commits proof без повторного Chromium/build/security pipeline на metadata-only event.
## Evidence
Audit date `2026-10-11`; [11](https://git.personal.ksv741.ru/WealthLedger/main/src/commit/d07fbfabb1295780952a554185989d2d5b5c8349/audits/2026-10-11/reports/11-validation-and-ci-cd-efficiency-report.md), VERIFY-002 (frontend). Revision `c8821200ce699dab1ce65360d1968d5877a2e78b`; Confidence High static config; Verification status static/server behavior unverified.
Affected: [.gitea/workflows/verify.yml:3–37](https://git.personal.ksv741.ru/WealthLedger/frontend/src/commit/c8821200ce699dab1ce65360d1968d5877a2e78b/.gitea/workflows/verify.yml#L3-L37); README:116–120. Root commits.yml edited precedent существует; сервер 1.27.3.
## Scope
### In scope
Existing metadata event/title job и required contexts verification.
### Out of scope
Full pipeline на edited, новый event classifier, отключение required checks.
## Proposed Approach
Selective commits execution; skipped downstream jobs не должны обходить failed required proof. Сверить actual Gitea protection/status behavior.
## Acceptance Criteria
- [ ] Invalid title-only rename обновляет commits в FAIL, valid rename — PASS на том же HEAD.
- [ ] Metadata-only event не запускает app verify/build/Chromium.
- [ ] Existing required contexts достижимы; normal code PR по-прежнему проходит полный pipeline.
## Verification
Disposable PR title changes и read-only protection/status inspection; workflow syntax review. Не запускать full project verify ради YAML, если app inputs unchanged.
## Dependencies
Нет; другие repository title fixes независимы.
## Traceability
Campaign https://git.personal.ksv741.ru/WealthLedger/main/issues/23 . Finding VERIFY-002. WealthLedger/frontend; T34 frontend.
codex-bot
added this to the Technical Audit Remediation — 2026-10-11 milestone 2026-10-11 21:54:09 +03:00
Сделано в WealthLedger/frontend#84 (merged в develop): отдельный .gitea/workflows/pr-title.yml на pull_request: edited, только job commits с тем же контекстом. Проверено на одном HEAD: invalid title -> commits failure, valid title -> commits success; security и verify статусы не перезаписываются skipped.
Сделано в WealthLedger/frontend#84 (merged в develop): отдельный `.gitea/workflows/pr-title.yml` на `pull_request: edited`, только job `commits` с тем же контекстом. Проверено на одном HEAD: invalid title -> commits failure, valid title -> commits success; security и verify статусы не перезаписываются skipped.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
PR opened/synchronize/reopened triggers не включают edited. После invalid title rename прежний green commits остаётся; README обещает title check. Это metadata-policy gap P3, не runtime incident.
Expected Behavior
Changed PR title получает свежий commits proof без повторного Chromium/build/security pipeline на metadata-only event.
Evidence
Audit date
2026-10-11; 11, VERIFY-002 (frontend). Revisionc8821200ce699dab1ce65360d1968d5877a2e78b; Confidence High static config; Verification status static/server behavior unverified.Affected: .gitea/workflows/verify.yml:3–37; README:116–120. Root commits.yml edited precedent существует; сервер 1.27.3.
Scope
In scope
Existing metadata event/title job и required contexts verification.
Out of scope
Full pipeline на edited, новый event classifier, отключение required checks.
Proposed Approach
Selective commits execution; skipped downstream jobs не должны обходить failed required proof. Сверить actual Gitea protection/status behavior.
Acceptance Criteria
Verification
Disposable PR title changes и read-only protection/status inspection; workflow syntax review. Не запускать full project verify ради YAML, если app inputs unchanged.
Dependencies
Нет; другие repository title fixes независимы.
Traceability
Campaign WealthLedger/main#23 . Finding VERIFY-002. WealthLedger/frontend; T34 frontend.
Сделано в WealthLedger/frontend#84 (merged в develop): отдельный
.gitea/workflows/pr-title.ymlнаpull_request: edited, только jobcommitsс тем же контекстом. Проверено на одном HEAD: invalid title -> commits failure, valid title -> commits success; security и verify статусы не перезаписываются skipped.