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
@@ -60,18 +60,10 @@ export const analyzeJavaScriptApplicationValidated = async (
|
||||
options.signal,
|
||||
);
|
||||
const { electron_summary: summary, ...application } = reconstructed;
|
||||
const contradictions = reconstructed.integrity_contradictions.length;
|
||||
const result = javascriptApplicationAnalysisResultSchema.parse({
|
||||
...application,
|
||||
summary,
|
||||
limitations: [
|
||||
...reconstructed.graph.limitations,
|
||||
...(contradictions === 0
|
||||
? []
|
||||
: [
|
||||
`${String(contradictions)} artifact file(s) contradict declared integrity; their observed bytes are untrusted, and contradicted nested archives were not expanded.`,
|
||||
]),
|
||||
],
|
||||
limitations: reconstructed.graph.limitations,
|
||||
});
|
||||
await options.progress?.report({
|
||||
phase: "analyze_javascript_application",
|
||||
|
||||
Reference in New Issue
Block a user