release(#401): v2.0.2 by atlas-apex · Pull Request #402 · me2resh/apexyard

atlas-apex · 2026-05-24T17:14:26Z

v2.0.2 — 2026-05-24

PATCH release. GA4 + cookie-consent banner now fire on all 4 site pages (was only / in v2.0.0 + v2.0.1). No framework code touched — site-only.

This PR will tag v2.0.2 on main after merge.

Fixed

fix(#399) GA4 tag on all 4 site pages — copied gtag.js + Consent Mode v2 default block from index.html to how-it-works.html, architecture.html, skills.html. Each block wrapped in  ...  markers for greppable future sync (static site, no build step). Every share-driven visit now tracked (subject to consent).
fix(#399) Cookie consent banner on all 4 site pages — same Accept/Decline/Escape flow + localStorage.ay-consent persistence as the existing index.html implementation. A user landing on /how-it-works first now gets the consent choice; the choice is honoured site-wide on subsequent navigation. Closes the GDPR gap where a non-index entry-pointed user had no consent UI at all.
fix(#399) Removed dead 'anonymize_ip': true from gtag('config', ...) — no-op in GA4 (Universal Analytics carryover; GA4 anonymizes all IPs by default).
fix(#399) Refreshed <meta name="llm:token-count"> + <meta name="llm:doc-length"> on all 4 pages to reflect post-fix sizes so token-budget-aware LLM clients see accurate costs.

Compatibility

No breaking changes. No framework code touched. Adopters see no changes to hooks, skills, rules, agents, templates, or workflows — only site/ files modified.

Release strategy

Branched release/v2.0.2 from upstream/main (which already contains the fix as commit b29b266 from merged PR #400). Two small commits on the release branch: the GA4/consent fix already on main, plus this PR's CHANGELOG + version-pill bump.

main→dev sync continues to be a deferred follow-up — same compounding divergence as v2.0.1; will fold into the next release that needs dev's work, or be done as a standalone sync PR.

AgDR note

 marker present at the top: release PRs are pure version-cuts with no architectural decisions. The underlying fix (#399 / PR #400) was already shipped as a cosmetic HTML/CSS/JS copy-paste with the same skip marker.

Leak-protection skip note

 marker present at the top: the body legitimately references yard.apexscript.com, the framework's own public marketing domain. Same recurring false-positive as the v2.0.0 / v2.0.1 launch PRs and #400.

Multi-close note

 marker present at the top, even though this PR only has one Closes line (#401). #399 already auto-closed on PR #400's merge to main; we're not re-closing it here. The marker is present out of habit for release PRs — defensive against any future additions.

Testing

bash .claude/hooks/tests/test_site_counts.sh — PASS (all scanned files within 5% of actuals after version-pill change)
git log upstream/main..HEAD shows exactly 1 commit on the release branch (CHANGELOG + version-pill bump). The GA4 fix is already on main via PR fix(#399): site/ — GA4 + consent banner on all 4 pages #400.
CHANGELOG appended above [2.0.1] with parallel structure (heading shape, Fixed/Compatibility subsections)
Site version link updated v2.0.1 → v2.0.2 (resolves to a real tag after this PR merges)
Netlify deploy preview will surface from this PR — visual check of consent banner rendering on each page (4 across)
Post-merge: GA4 Realtime should show traffic on /how-it-works, /architecture, /skills once the tag is live and Netlify re-deploys from main
After merge: v2.0.2 tag pushed to upstream/main
After merge: GitHub Release created with CHANGELOG section
After merge: drift banner on adopters' forks fires on next session

Glossary

Term	Definition
PATCH bump	Semver third-position increment (X.Y.Z+1). Applied when only `fix:` commits are included since the last tag — no new features, no breaking changes.
Release-cut branch model	apexyard's framework-only flow: daily PRs land on `dev`; `main` only receives release PRs from `dev` (tagged with semver). v2.0.1 + v2.0.2 used the cherry-pick / direct-to-main shape because of carried dev divergence; the canonical flow returns once dev catches up.
dev/main squash divergence	When a release PR is squash-merged to main, the resulting commit has a different SHA than the equivalent dev history. dev still carries the unsquashed commits unless a sync-back PR is filed. v1.2.0, v1.3.0, v2.0.0 all created this gap; v2.0.1 + v2.0.2 didn't add new divergence (the fixes went directly to main).
GA4 + Consent Mode v2	Google Analytics 4 with Google's consent-mode default declaring `analytics_storage: 'denied'` until the user clicks Accept. Required for GDPR-compliant EU traffic.

Closes #401

- Append [2.0.2] section above [2.0.1] - Bump site/index.html version pill v2.0.1 → v2.0.2 - Site-only release; framework unchanged - Underlying fix: #399 / PR #400 (GA4 + consent on all 4 pages) Refs #401

netlify · 2026-05-24T17:14:30Z

✅ Deploy Preview for apexyard ready!

Name	Link
🔨 Latest commit	`44001e5`
🔍 Latest deploy log	https://app.netlify.com/projects/apexyard/deploys/6a1331f452170c000883c3da
😎 Deploy Preview	https://deploy-preview-402--apexyard.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

atlas-apex

Code Review: PR #402

Commit: 44001e5da5d90248cddac320827c9dcf746dbc7f

Summary

v2.0.2 PATCH release-cut. Two files, narrow scope: appends a structurally-parallel ## [2.0.2] section to CHANGELOG.md and bumps the homepage version pill from v2.0.1 → v2.0.2. The underlying GA4-on-all-pages fix (#399 / PR #400 / commit b29b266) is already on main; this PR is purely the version-cut wrapper.

Checklist Results

Architecture & Design: N/A (no framework code touched)
Code Quality: Pass
Testing: N/A (site-counts drift detector PASS, markdownlint PASS, lychee PASS)
Security: Pass
Performance: N/A
PR Description & Glossary: Pass — 4 non-trivial glossary terms
Summary Bullet Narrative: Pass
Technical Decisions (AgDR): N/A — pure version-cut, marker justified
Adopter Handbooks: N/A — no triggers

Diff scope verification

CHANGELOG.md     +17 -0
site/index.html  +1  -1

Zero framework code. No carry-over of the GA4 fix from PR #400 — clean.

CHANGELOG parity

New ## [2.0.2] — 2026-05-24 block mirrors ## [2.0.1] directly below: same heading shape, prose lead, ### Fixed bullet pattern using `fix(#NNN)` **<bold>** — <rationale>, same ### Compatibility paragraph.

Version pill

Line 1576: anchor href updated to .../releases/tag/v2.0.2, inner text v2.0.2. Styling, target, rel unchanged. Byte-equal length — site-counts detector passes.

Skip markers

All three justified: private-refs: allow (apexscript.com marketing domain), multi-close: approved (defensive — one Closes line), agdr: not-applicable (pure version-cut).

CI status

All required checks green.

Issues Found

None.

Verdict

APPROVED

Reviewed by Rex (Code Reviewer Agent)
Reviewed commit: 44001e5da5d90248cddac320827c9dcf746dbc7f

…h#402) - Append [2.0.2] section above [2.0.1] - Bump site/index.html version pill v2.0.1 → v2.0.2 - Site-only release; framework unchanged - Underlying fix: me2resh#399 / PR me2resh#400 (GA4 + consent on all 4 pages) Refs me2resh#401 Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com>

chore(#401): CHANGELOG v2.0.2 + site version pill bump

44001e5

- Append [2.0.2] section above [2.0.1] - Bump site/index.html version pill v2.0.1 → v2.0.2 - Site-only release; framework unchanged - Underlying fix: #399 / PR #400 (GA4 + consent on all 4 pages) Refs #401

github-actions Bot added github-issue has-ticket labels May 24, 2026

atlas-apex commented May 24, 2026

View reviewed changes

atlas-apex merged commit eb41cfe into main May 24, 2026
8 checks passed

atlas-apex deleted the release/v2.0.2 branch May 24, 2026 17:19

OmarEhab007 mentioned this pull request May 25, 2026

chore: sync ops fork with upstream apexyard v2.1.0 #412

Closed

3 tasks

HOSS11H mentioned this pull request May 30, 2026

chore(#2): sync ops fork with upstream apexyard v2.2.0 HOSS11H/apexyard#3

Merged

5 tasks

osama-abu-baker mentioned this pull request May 31, 2026

chore(ITH-210): sync ops fork with upstream apexyard v1.2.0→v2.2.0 #467

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

release(#401): v2.0.2#402

release(#401): v2.0.2#402
atlas-apex merged 1 commit into
mainfrom
release/v2.0.2

atlas-apex commented May 24, 2026

Uh oh!

netlify Bot commented May 24, 2026 •

edited

Loading

Uh oh!

atlas-apex left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

atlas-apex commented May 24, 2026

v2.0.2 — 2026-05-24

Fixed

Compatibility

Release strategy

AgDR note

Leak-protection skip note

Multi-close note

Testing

Glossary

Uh oh!

netlify Bot commented May 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for apexyard ready!

Uh oh!

atlas-apex left a comment

Choose a reason for hiding this comment

Code Review: PR #402

Summary

Checklist Results

Diff scope verification

CHANGELOG parity

Version pill

Skip markers

CI status

Issues Found

Verdict

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

netlify Bot commented May 24, 2026 •

edited

Loading