chore(recon): neutralize internal/competitive framing in source comments

Public-repo hygiene pass:
- engine.go: drop named-person attribution from a scope comment (kept the
  pdpv0-only technical rationale)
- datapath.go / datapath_test.go / dashboard.go / squid.go: remove
  competitive comparisons to an unreleased upstream effort; keep the
  technical substance (env aliases, panel behavior, headless USDFC flow)

No functional change; comments only (plus one test comment).

Author: Reiers

internal/dashboard/dashboard.go

@@ -208,8 +208,8 @@ type overviewChain struct {
 	HeadEpoch int64
 	NetworkID string
 
-	// Chain Connectivity + Chain Node Network panels (Skiff-parity, but
-	// served entirely off the embedded Lantern = a live zero-Glif proof).
+	// Chain Connectivity + Chain Node Network panels, served entirely off
+	// the embedded Lantern = a live zero-Glif proof.
 	// All fields are best-effort; a nil/unavailable eth client leaves
 	// them at zero/empty and the panel renders graceful placeholders.
 	RPCAddress   string // embedded Lantern in-process RPC endpoint

internal/datapath/datapath.go

@@ -4,17 +4,15 @@
 // mounted disk and curio-core will find and use it — no flags, no
 // config file, no DB host.
 //
-// This is the "it just works" onboarding touch: parity with (and a
-// superset of) the labelled-folder discovery described for Curio's
-// Skiff build, except here it is actually implemented and tested,
-// CGO-free, and works on linux + darwin.
+// This is the "it just works" onboarding touch: labelled-folder
+// discovery, CGO-free, working on linux + darwin.
 //
 // Resolution precedence (first hit wins):
 //
 //  1. explicit path        — the --data-storage flag / Resolve(explicit=...)
 //  2. env CURIO_PDP_DATA   — primary env override
-//  3. env DATA_STORAGE     — Skiff-compatible alias
-//  4. env CURIO_DATA       — Skiff-compatible alias
+//  3. env DATA_STORAGE     — compatibility alias
+//  4. env CURIO_DATA       — compatibility alias
 //  5. labelled folder      — a directory named LabelDir ("curio-pdp-data")
 //     found within MaxDepth levels of any real mountpoint, preferring
 //     the mount with the most free space (so big data disks win over /)

internal/datapath/datapath_test.go

@@ -29,7 +29,7 @@ func TestResolve_EnvPrecedence(t *testing.T) {
 		t.Fatalf("CURIO_PDP_DATA should win: got %+v", got)
 	}
 
-	// With CURIO_PDP_DATA unset, DATA_STORAGE (Skiff alias) wins next.
+	// With CURIO_PDP_DATA unset, DATA_STORAGE (compatibility alias) wins next.
 	t.Setenv("CURIO_PDP_DATA", "")
 	if got := Resolve("", "/fb"); got.Path != "/b" || got.Source != "env:DATA_STORAGE" {
 		t.Fatalf("DATA_STORAGE should win: got %+v", got)

internal/engine/engine.go

@@ -548,11 +548,10 @@ func (r *TaskRegistry) Len() int { return len(r.byName) }
 // carve-out fixes that). The static descriptors use `tasknames.PDPv0_*`
 // for naming consistency.
 //
-// Scope (2026-05-23, Andy via Nicklas): pdpv0-only. `tasks/pdp` (v1, the
-// mk20-deal-flow PDP) is intentionally NOT registered here. The v1
-// package + its `curio/market/mk20` transitive are out of scope for
-// curio-core. If v1 is reintroduced later, restore the safeCtors block
-// from git history at commit fd85e79.
+// Scope: pdpv0-only. `tasks/pdp` (v1, the mk20-deal-flow PDP) is
+// intentionally NOT registered here. The v1 package + its
+// `curio/market/mk20` transitive are out of scope for curio-core. If v1
+// is reintroduced later, restore the safeCtors block from git history.
 func BuildTaskRegistry() (*TaskRegistry, error) {
 	r := &TaskRegistry{byName: make(map[string]harmonytask.TaskTypeDetails, 32)}
 

internal/usdfcacquire/squid.go

@@ -8,8 +8,8 @@
 // quotes a Squid route (source-chain USDC -> Filecoin USDFC), signs the
 // returned source-chain transaction with the operator's own EVM key, and
 // broadcasts + tracks it to completion. The result lands USDFC directly in
-// the SP's PDP wallet on Filecoin -- fully headless, the thing Skiff/Easy-PDP
-// cannot do.
+// the SP's PDP wallet on Filecoin -- fully headless, no browser wallet
+// required.
 //
 // Squid contract: POST /v2/route returns a transactionRequest{target,data,
 // value,gasLimit}; GET /v2/status tracks the cross-chain fill. Both require