[Bug] Сохранить approved screener constraints в published OpenAPI #70
Closed
opened 2026-10-11 21:47:21 +03:00 by codex-bot
·
0 comments
No Branch/Tag Specified
Labels
Clear labels
Kind/Dependencies
Kind/Investigation
Kind/Process
Kind/Refactor
audit/2026-10-11
kind/investigation
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Dependency update or dependency-management work
Research or decision required before implementation
Developer workflow, CI/CD, tooling, or process improvement
Internal code or configuration restructuring without new product behavior
Technical Audit Remediation — 2026-10-11
Нужна проверка evidence до решения; runtime-дефект не утверждается
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Milestone
No items
No Milestone
Technical Audit Remediation — 2026-10-11
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: WealthLedger/backend#70
Reference in New Issue
Block a user
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
Published Criteria теряет additionalProperties:false, Item lot — minimum:1. Generator/runtime parity и frontend copies согласованы между собой, но не с target. Runtime unknown-field/invalid-lot outcome не воспроизводился; published schema drift подтверждён.
Expected Behavior
Оба constraints сохранены либо target owner явно reapproves изменение; consumer получает соответствующий artifact.
Evidence
Audit date
2026-10-11; 15, SPEC-005. Backend revision0ad84ff4f0b4712abc7e69dc299856f14af6eadd; specsfcdc805f6c1b3be6a20a7e858e3e80cbd83a9121; frontendc8821200ce699dab1ce65360d1968d5877a2e78b. Confidence High drift; Verification status static/runtime-unverified outcomes.Affected: stock.dto.ts:29–105; target:92–120, :174–177; frontend snapshot:7495–7573.
Scope
In scope
Два schema nodes, owner semantic comparison, configured HTTP boundary и explicit artifact delivery.
Out of scope
Registry/новый generator, mandatory sibling checkout CI, manual generated TS edits, автоматическая Finalization stock-screener.
Proposed Approach
Restore metadata/нужную runtime boundary либо explicit target reapproval. Existing raw-body allowlist не удалять: global/local pipe order важен.
Acceptance Criteria
Verification
Existing stocks.e2e-spec.ts, stock-screener/service tests, openapi-contract suite и consumer openapi:check. Сравнить target nodes явно: equality двух generated copies недостаточна.
Dependencies
Нет; contract decision нужен до закрытия active change, но этот Issue не делает archive.
Traceability
Campaign WealthLedger/main#23 . Finding SPEC-005. WealthLedger/backend; T37.