chore(release): 2.0.0-rc.3

[kherembourg]

Release 2.0.0-rc.3

Finalise la release 2.0.0-rc.3 en repliant tout le contenu [Unreleased] dans la section [2.0.0-rc.3] du CHANGELOG (confirmé : tout l'Unreleased appartient à rc.3). Les manifests étaient déjà épinglés à 2.0.0-rc.3.

Contenu de rc.3 (depuis le tag 2.0.0-rc.2)

Added

• Skill portable purchasely-sdk-expert pour les questions libres sur le SDK (Q&A expert dans les installs skills-only, sans le subagent Claude Code).

Changed

• Toutes les skills passent à l'API builder Flutter v6 (PurchaselyBuilder, PresentationBuilder/PresentationRequest, interceptAction + InterceptResult, presentation.close(), synchronize() awaitable). RN & Cordova restent en v5 (5.7.3).
• references/flutter/* et references/sdk-versions.md réécrits/épinglés sur 6.0.0-rc.1.
• purchasely-migrate migre aussi Flutter v5.x → 6.0.0-rc.1.
• Agent renommé sdk-expert → purchasely-sdk-expert (wrapper de la skill portable).
• README : Claude Code = install full recommandée ; npx skills add = install skills-only (5 skills, sans subagent/hooks/commands).
• Les skills routent vers purchasely:purchasely-sdk-expert quand le subagent est dispo, sinon checkpoint inline.

Fixed

• Corrections snippets Flutter v6, interceptor de login, paywalls gelées, snippet promo Observer-mode, alignement des versions manifests sur 2.0.0-rc.3.

Removed

• Purchasely.presentSubscriptions() retiré côté Flutter v6.
• Commande slash /purchasely:question retirée.

Vérifications

• npm test (guard known-bad snippets) ✅
• Manifests plugin.json + package.json à 2.0.0-rc.3 ✅
• Aucune référence rc.1/rc.2 résiduelle hors CHANGELOG ✅

Le tag 2.0.0-rc.3 sera posé après merge sur main.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR finalises the 2.0.0-rc.3 release entry in CHANGELOG.md by folding all [Unreleased] content (Added, Changed, Fixed, Removed sections) into a single [2.0.0-rc.3] versioned section, leaving [Unreleased] empty as a placeholder for future work. Only CHANGELOG.md is touched.

• Merged the standalone rc.3 Changed/Removed entries with the previously Unreleased Added/Changed/Fixed/Removed entries into one coherent [2.0.0-rc.3] block dated 2026-06-17.
• Updated the Flutter v6 Changed bullet to reference purchasely-sdk-expert (the renamed agent) instead of the old sdk-expert name.
• Reordered the two Removed items so presentSubscriptions() leads and the /purchasely:question slash-command removal follows.

Confidence Score: 5/5

Documentation-only change to CHANGELOG.md with no functional code touched — safe to merge.

The entire diff is a CHANGELOG reorganisation: Unreleased items are folded into a versioned rc.3 entry, the superseded standalone rc.3 block is removed, and one agent name reference is corrected. No production code, configuration, or skill files are modified. The only nit is a missing [Unreleased] comparison link at the footer, which is a cosmetic convention gap with no runtime impact.

No files require special attention.

Important Files Changed

Filename	Overview
CHANGELOG.md	Collapses [Unreleased] into the [2.0.0-rc.3] versioned section, adds Added/Fixed entries from the unreleased block, and removes the superseded standalone rc.3 entry — correct Keep a Changelog structure; no code changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["CHANGELOG.md — before PR"] --> B["## [Unreleased]\nAdded / Changed / Fixed / Removed"]
    A --> C["## [2.0.0-rc.3] — 2026-06-17\nChanged / Removed (rc.3 only)"]
    A --> D["## [2.0.0-rc.2] — 2026-06-16"]

    E["CHANGELOG.md — after PR"] --> F["## [Unreleased]\n(empty placeholder)"]
    E --> G["## [2.0.0-rc.3] — 2026-06-17\nAdded + Changed (merged) + Fixed + Removed (merged)"]
    E --> H["## [2.0.0-rc.2] — 2026-06-16"]

    B -- "collapsed into" --> G
    C -- "replaced by" --> G

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["CHANGELOG.md — before PR"] --> B["## [Unreleased]\nAdded / Changed / Fixed / Removed"]
    A --> C["## [2.0.0-rc.3] — 2026-06-17\nChanged / Removed (rc.3 only)"]
    A --> D["## [2.0.0-rc.2] — 2026-06-16"]

    E["CHANGELOG.md — after PR"] --> F["## [Unreleased]\n(empty placeholder)"]
    E --> G["## [2.0.0-rc.3] — 2026-06-17\nAdded + Changed (merged) + Fixed + Removed (merged)"]
    E --> H["## [2.0.0-rc.2] — 2026-06-16"]

    B -- "collapsed into" --> G
    C -- "replaced by" --> G

Loading

Comments Outside Diff (1)

1. CHANGELOG.md, line 115 (link)

   Keep a Changelog convention recommends a comparison link for the [Unreleased] section so readers can click through to see what has landed on the default branch since the last tag. Now that 2.0.0-rc.3 is being tagged, adding this link keeps the footer consistent with the other version entries.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: CHANGELOG.md
   Line: 115
   
   Comment:
   Keep a Changelog convention recommends a comparison link for the `[Unreleased]` section so readers can click through to see what has landed on the default branch since the last tag. Now that `2.0.0-rc.3` is being tagged, adding this link keeps the footer consistent with the other version entries.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
CHANGELOG.md:115
Keep a Changelog convention recommends a comparison link for the `[Unreleased]` section so readers can click through to see what has landed on the default branch since the last tag. Now that `2.0.0-rc.3` is being tagged, adding this link keeps the footer consistent with the other version entries.

```suggestion
[Unreleased]: https://github.com/Purchasely/Purchasely-AI-Plugin/compare/2.0.0-rc.3...HEAD
[2.0.0-rc.3]: https://github.com/Purchasely/Purchasely-AI-Plugin/releases/tag/2.0.0-rc.3
```

_{Reviews (1): Last reviewed commit: "chore(release): 2.0.0-rc.3" | Re-trigger Greptile}

[kherembourg]

Release mergée directement sur main (pas de PR pour les releases sur ce repo).