Address #202 review: fix two inaccurate code comments

- set-plan-status.js: a crash between the HTML-then-JSON renames leaves "HTML ahead
  of JSON" (new HTML, old JSON), not "JSON behind HTML". Reworded to the correct
  direction (it's the inverse of the original pre-atomic bug; benign + self-healing).
- estimate-solution-size.js: the marker probe was said to be "documented in
  CLAUDE.md"; point at the canonical source (detect-project-context.js, also in
  AGENTS.md) instead.

Comment-only; no behavior change.

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

Author: tyaginidhi

plugins/power-pages/scripts/lib/estimate-solution-size.js

@@ -84,7 +84,8 @@ function parseArgs(argv) {
 // Resolve the build-axis site type for the estimator's diagnostic `siteType`
 // output field. Prefer the caller-supplied value (plan-alm resolves this in
 // Phase 1 via detect-project-context.js, the authoritative source), and fall
-// back to a lightweight local probe of the same markers documented in CLAUDE.md:
+// back to a lightweight local probe of the same markers detect-project-context.js
+// resolves on (also described in the plugin's AGENTS.md "detect-project-context.js" entry):
 //   - `powerpages.config.json`          → code / SPA site
 //   - `.powerpages-site/.portalconfig/` → declarative design-studio (EDM/standard) site
 // Returns the canonical values ('code' | 'declarative') to match

plugins/power-pages/scripts/lib/set-plan-status.js

@@ -161,9 +161,12 @@ function setPlanStatus(opts) {
       try { fs.unlinkSync(htmlTmp); } catch {}
       throw e;
     }
-    // Both products are ready: commit the HTML then the JSON. (Same-dir renames in
-    // one process; a failure between them is vanishingly unlikely and would at worst
-    // reproduce the pre-existing "JSON behind HTML" state, never a torn JSON file.)
+    // Both products are ready: commit the HTML then the JSON. A crash BETWEEN these
+    // two same-dir renames (vanishingly unlikely in one process) would leave the new
+    // HTML in place with the JSON still old — "HTML ahead of JSON". That's benign and
+    // self-healing: the next render re-derives the HTML from whatever the JSON says,
+    // and no file is ever torn (each rename is atomic). It is the inverse of the
+    // original pre-atomic bug (new JSON + stale HTML), and harmless in the same way.
     fs.renameSync(htmlTmp, htmlPath);
     rendered = true;
   }