fix(artifacts): carry recorded integrity contradictions into application workflows
A recorded contradiction appeared only in the analyze_javascript_application response. Version and source comparisons, feature traces, and export-shape comparisons read the application graph, which still claimed complete coverage, so they could report complete-within-inputs results over untrusted bytes. The graph is now partial when contradictions were recorded, and its limitations, inherited by the result and the semantic graph, name every contradicted path. The mismatch remediation names both spellings: integrity_policy in MCP and --integrity-policy on the CLI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
92b373e660
commit
5aafaa00ec
@@ -58,6 +58,8 @@ interface BuilderInput {
|
||||
"graph_id" | "nodes"
|
||||
>;
|
||||
readonly analysis: JavaScriptArtifactAnalysis;
|
||||
/** Source facts the semantic graph inherits, such as integrity contradictions. */
|
||||
readonly sourceLimitations?: readonly string[];
|
||||
}
|
||||
|
||||
interface FileContext extends SemanticFlowProjectionContext {
|
||||
@@ -79,6 +81,7 @@ export const buildJavaScriptSemanticGraph = ({
|
||||
rootArtifactSha256,
|
||||
applicationGraph,
|
||||
analysis,
|
||||
sourceLimitations = [],
|
||||
}: BuilderInput): JavaScriptSemanticGraph => {
|
||||
const state = emptyState(applicationGraph);
|
||||
const fingerprints: JavaScriptSemanticGraph["fingerprints"][number][] = [];
|
||||
@@ -119,6 +122,7 @@ export const buildJavaScriptSemanticGraph = ({
|
||||
})),
|
||||
},
|
||||
limitations: [
|
||||
...sourceLimitations,
|
||||
"The semantic graph contains static syntax observations and conservative relationship candidates; it does not claim runtime execution.",
|
||||
"Local data flow does not claim control-flow-sensitive reaching definitions or arbitrary dynamic property resolution.",
|
||||
"Promise ownership covers explicit unshadowed Promise construction, static factories, aggregation, chaining, and await syntax only.",
|
||||
|
||||
Reference in New Issue
Block a user