fix(p07): classify Python API surfaces by evidence - #740
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
Validation checkpoint on exact GREEN head
Sequencing dependency is also reconciled: #679 is closed/completed, and #640 now records a source-architecture adjudication retaining Disposition remains |
ndrorchestration
marked this pull request as ready for review
September 16, 2026 15:39
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Address issue #659 narrowly: stop treating every
api/*.pytarget as a HIGH deprecated-stub candidate solely because it is Python, while preserving actionable HIGH detection for an actual same-purpose Python/Pages API collision.TDD evidence
RED test-only head:
bf2e8747cf2e27e227fa09ff8389a3389a99f1ee.At that exact head, UI Command Center Validation run
35115525212failed atRun UI semantic and contract tests; the production application build was skipped. That is the preserved intended RED checkpoint before the detection module existed.A separate PR Issue-State Keyword Guard failure on the RED head came from closure-keyword syntax in the PR description, not product code; the description was corrected before GREEN.
GREEN implementation head:
19f9682f435cfb5279acc94c284455600379385f.Fresh exact-head verification on GREEN returned 19 workflow families, all terminal SUCCESS:
UI Command Center Validation run
35115803504passed both the semantic/contract tests and the production application build on the exact GREEN head.Implementation
app/lib/sweep-detection.tsmodule;api/ahg_herald.pyvisible but INFO rather than falsely HIGH solely because it is Python;api/<name>.py+pages/api/<name>.tspair HIGH;requirements.txtfindings;harmonic_score: null / NOT_COMPUTEDsemantics;Runtime-architecture adjudication
Issue #640 now records the source-architecture disposition that
api/ahg_herald.pyremains an intentional P-01 Python runtime surface unless explicitly superseded. That source classification does not establish current production validation; #729 separately owns exact-current production-runtime reconciliation.Non-effects
Detection-quality/UI-tool correctness only. No materialization, authorization, efficacy, independent-validation, High-Assurance, or scientific-N transition is created by this PR.