orchestrator: resolve the engine at the caller, not in the summary builder

compute_kaslr_info() called engine_resolve() and the sync itself, so a function
named for building a summary also owned when the engine ran. Its five
KASLD_TESTING blocks all hung off that: they reached file-static engine globals
the testing translation unit does not link, so 202 of the function's 382 lines -
53% - were cut out of the very binary that tests it, and each quantity gaining a
render sink widened the gap further.

Take the two resolutions as PARAMETERS instead. struct engine was already in a
header and struct engine_resolution is plain data, so the types are universal
even where the instances are not; the gates become runtime `if (auth)` /
`if (likely)`, and the resolution moves to emit_summary(), the single caller.
compute_kaslr_info() now carries zero KASLD_TESTING blocks and compiles whole in
every build.

Not merely tidier: test_compute_kaslr_info_engine_pin_overrides_raw_anchor
constructs a snapshot with a pinned estimate and asserts it beats the
verdict-blind anchor scan. That test could not have been written before, because
the code it exercises did not exist in this binary. Disabling the reconcile
fails it.

One hazard the move introduced and closed: a block dereferenced the likely
snapshot under the auth guard. kasld_reconcile_concrete_base reads the likely
edges only under have_likely, so a zeroed stand-in is sound; every auth-> and
likely-> use was then audited against the guard it sits under.

Author: bcoles

src/include/kasld/internal.h

@@ -887,7 +887,19 @@ int meta_get_all(const struct component_meta *m, const char *key,
                  const char **values, int max_values);
 void inject_kaslr_defaults(struct summary *s);
 void compute_component_stats(struct summary *s);
-void compute_kaslr_info(struct summary *s);
+/* Declared at file scope: first naming these inside the parameter list below
+ * would give them PROTOTYPE scope -- a distinct type from the definition in
+ * orchestrator.c, which the compiler then reports as a conflicting declaration.
+ */
+struct engine;
+struct engine_resolution;
+
+/* Projects `layout` plus the engine's two resolutions into the summary. The
+ * snapshots are PARAMETERS, not globals: the resolution itself belongs to the
+ * caller, and passing them keeps this whole function compiled -- and testable
+ * -- in the build that does not link the engine, where a caller passes NULL. */
+void compute_kaslr_info(struct summary *s, const struct engine *auth,
+                        const struct engine_resolution *likely);
 
 /* =========================================================================
  * Rendering (defined in render.c)