docs(skill): follow magic_starter off the alpha rail - #155
Conversation
magic_starter's next release is 0.0.27 rather than 0.0.1-alpha.27, so the reference stamp moves with it and the release markers inside the file read 0.0.27 where they described that release. Its magic_notifications requirement moves to ^0.3.0, the floor the starter release carries. The notification section gains the five notifications.* keys the mounted screens read and no package supplies: bulk_title, bulk_description, delete, delete_failed and channel_sms. An adopter upgrading with a hand-written catalogue sees each rendered as its own key, and this file is the only agent-facing document for that package because .pubignore keeps its CLAUDE.md out of the published archive. SKILL.md's version moves to 0.1.17 because reference content moved.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Note Kodizm (AI-generated). May contain mistakes; verify before acting. Markdown-only stamp and content update that checks out: the pub-resolution claim, the translation keys, and the changelog placement are all accurate; one small internal inconsistency left over. Minor
Notes (not blocking)
TestsNo test covers the reference text, and this repo has no stamp assertion for it ( Checks I ran
|
Three commits landed on that package's main after the stamp move was written (#130, #131, #132), all into the same unreleased section, so the release this file is stamped for now ships more than it described. The configuration block gains notifications.external_id_prefix and a paragraph on the identity lifecycle: the provider declares <prefix><user id> off Auth.stateNotifier, releases it when a session ends, and reads the current state once at boot. The value has to equal the backend's own, since OneSignal accepts a mismatch and delivers to nobody, so the only trace is a zero-recipient report on the server. starter:doctor reports the resolved prefix and never fails on it, because three of the four sites that compose the id live in magic-starter-laravel. Also records that polling now stops on the two sign-outs the auth controller never sees, which is the one behaviour an app could notice.
|
Note Kodizm (AI-generated). May contain mistakes; verify before acting. Incremental re-review of TestsStill markdown-only, still nothing in this repo asserting the reference text (the stamp test lives in Checks I ran
My earlier minor note on the troubleshooting row ( |
1 participant
magic_starterleaves the alpha rail at its next release (fluttersdk/magic_starter#129):0.0.1-alpha.26is followed by0.0.27, carrying the counter rather than resetting it. This is the sibling half of that change.skills/magic-framework/references/plugin-starter.mdis the only agent-facing document that package has, since.pubignorekeeps itsCLAUDE.mdand.claude/out of the published archive, and it is versioned by THIS repo's releases rather than by that package's.magic_starter/test/skill_reference_stamp_test.dartfails against a stale stamp whenever a sibling checkout exists, so this file has to move in step.What changed
v0.0.1-alpha.27tov0.0.27, and the(alpha.27)release marker on the intended-url paragraph reads(0.0.27). The older markers (alpha.19, alpha.22, alpha.23, alpha.25) are left alone: those releases really were named that, and the file uses them as history.magic_notificationsrequirement moves from^0.2.0to^0.3.0, which is the floor the starter release carries.0.0.27arrive after0.0.1-alpha.26and needs to know an existing^0.0.1-alpha.Npin already covers it (a caret on a zero major ends at0.1.0).notifications.*keys the mounted screens read and no package supplies:bulk_title,bulk_description,delete,delete_failed,channel_sms.starter:installscaffolds them; an upgrade with a hand-written catalogue renders each key as its own text until they are added by hand.SKILL.mdversion0.1.16to0.1.17, per the rule that it moves when reference content moves.Markdown only, no source or test touched.
Author: Anılcan Çakır anilcan.cakir@gmail.com