Analyse the uploaded software materials using the selected software workflow.

Separate clearly between:
- directly observed code or configuration evidence
- runtime evidence such as logs, traces, or failures
- inferred risks or architectural implications
- missing validation or missing context

Do not invent code, APIs, runtime behavior, or infrastructure that is not present in the supplied material.

Focus on:
- the highest-risk technical findings
- likely correctness or regression issues
- architecture stress points and coupling risks
- rollout or reliability concerns
- missing tests, validation, or context
- the most decision-relevant information gaps

If the run is review-focused, prioritize defects, regressions, unsupported assumptions, and validation gaps.
If the run is architecture-focused, map boundaries, coupling, flow, stress points, and unresolved structural ambiguity.
If both are selected, produce a combined technical report without turning the output into a full implementation plan.

End with:
- executive summary
- highest-signal issues
- strongest technical risks
- most important missing validation or context
- best next review questions