This stabilization pass tightened two separate delivery layers without changing the creator site’s canonical identity or replacing existing social evidence.
Rendered crawler semantics
The Meta noscript tracking request still remains available for its intended measurement role, but the rendered one-pixel image is now explicitly presentation-only. Post-build HTML normalization clears its alternative text, retains aria-hidden="true", and adds role="presentation", so text extractors and crawlers do not mistake a tracking request for authored page imagery. Ordinary content images keep their existing semantics.
A dedicated page-delivery regression test now locks that behavior while also checking that the tracking request URL itself remains intact.
Bounded social-content ingestion
The independent social-poller now normalizes recent-post samples into deterministic newest-first order with stable tie-breaks. Identical same-observation retries stay idempotent; a corrected payload using the same observation timestamp can replace stale latest values without creating a zero-duration trend. Creator-path checks were tightened where a platform permalink exposes account identity, title validation now happens after control-character cleanup, and publication timestamps must be causally compatible with their observation time.
The existing explicit-empty replacement behavior remains intact so an intentional empty sample can still withdraw previously published recent posts. A history regression that depended on the current UTC hour was also made deterministic across midnight boundaries.
Validation evidence
Creator-site validation passed 17 page-delivery tests, 7 feed-delivery tests, 49 feature and Worker tests, the static Astro build, the rendered-release audit covering 29 canonical pages, the built robots.txt source check, and the Wrangler deployment dry run. The independent social-poller validation run also passed its unit tests, generated-type and TypeScript checks, primary Worker dry run, and Stratus Worker dry run.
The locked full development install still reports three high-severity findings in tooling dependencies, but the new production-dependency gate reports zero vulnerabilities with npm audit --omit=dev --audit-level=high. CI now preserves that distinction instead of treating build-tool maintenance warnings as shipped browser-runtime findings. No forced dependency upgrade was applied merely to silence the development audit.