chore(webapp): drop internal phase labels from mollifier route comments

Comments referenced internal phase labels ("Phase A2", "Phase A5") from
the development plan rather than describing what the code does. Replaced
with self-contained prose; the surrounding explanations were already
correct and are preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: d-cs

apps/webapp/app/routes/api.v1.runs.$runId.spans.$spanId.ts

@@ -16,12 +16,12 @@ const ParamsSchema = z.object({
   spanId: z.string(),
 });
 
-// Phase A2 — discriminated union for PG vs buffered runs. Buffered runs
-// only have one valid spanId (the queued span recorded at gate time and
-// reused as the run's root spanId when the drainer materialises). Any
-// other spanId returns a deterministic 404; the queued span returns a
-// minimal synthesised shape so the customer's SDK sees the same 200
-// contract they'd get for a freshly-triggered run.
+// Resolve the run from either Postgres or the mollifier buffer.
+// Buffered runs only have one valid spanId (the queued span recorded at
+// gate time and reused as the run's root spanId when the drainer
+// materialises). Any other spanId returns a deterministic 404; the queued
+// span returns a minimal synthesised shape so the customer's SDK sees the
+// same 200 contract they'd get for a freshly-triggered run.
 type ResolvedRun =
   | { source: "pg"; run: Awaited<ReturnType<typeof findPgRun>> & {} }
   | { source: "buffer"; run: NonNullable<Awaited<ReturnType<typeof findRunByIdWithMollifierFallback>>> };

apps/webapp/app/routes/api.v1.runs.$runParam.attempts.ts

@@ -18,11 +18,11 @@ const ParamsSchema = z.object({
   runParam: z.string(),
 });
 
-// Phase A5 — fixes the pre-existing route bug where GET on this URL
-// returned a Remix "no loader" 400 with an internal error message. The
-// route only exposed `action` (POST creates a new attempt); GET had no
-// handler, so any well-intentioned SDK probe hit the framework error
-// instead of a proper API response.
+// GET handler added to fix the pre-existing route bug where this URL
+// returned a Remix "no loader" 400 with an internal error message — only
+// `action` (POST creates a new attempt) was exported, so any
+// well-intentioned SDK probe hit the framework error instead of a proper
+// API response.
 //
 // Returns `{ attempts: [] }` for both PG and buffered runs. The detailed
 // attempt list belongs on the v3 retrieve endpoint, not here — this is