Repository navigation
SIMAI Framework IntelliSense 0.3.0: repin to ui-132b0863e12b - #3
Merged
Merged
Conversation
The Framework now promotes registry entries by a written rule, so the suggestion set grew from 36 to 170 of 345 entries: 51 tags (was 13), 9270 utility classes (was 1058) and 973 tokens (was 922). sf-list-item and the other promoted components complete on their own; sf-button-group, sf-inline-editor and sf-toggle stay held and so stay known but unsuggested. The sizing contract is unchanged at simai.vertical-sizing@1.3.0. The generator now refuses a registry that promotes an entry its own readiness does not call ready: the index and the per-entry state are written by the same build, so a disagreement is a defect to look at and not something to settle quietly in favour of the wider set. Modal is safe to suggest in this release, so sf-modal-dialog joins the snippets. The extension suite waits for activation before its first request, which is what that test was always about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Each scene used to sleep and then grab the whole window: a shot could land on a "Loading…" suggest widget or a half-faded hover, and the band was mostly empty editor. The capture now waits for the widget to hold its rows, lets it settle, and clips to the last row at 2x. Two runs produce the same six sizes. The images are retaken at the release ui-32c7a64e4575, so they show the widened tag list, the md:flex utilities and the new release in the hover. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The release the owner picked for 0.3.0: registry simai/ui@ef384677, runtime simai/ui@132b0863 for both core and smart, sizing contract from simai/ui-source@6b16b41d (simai.vertical-sizing@1.3.0, unchanged). The Framework now promotes 136 entries by its written rule and the button group is no longer held, so safe_to_suggest is 172 of 345: 52 tags, 9270 utility classes and 980 tokens, 438 of them colours. The seven new tokens are the button group's public variables. sf-inline-editor and sf-toggle stay out of the suggestions and each held entry carries its reason in readiness.blockers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
zabarov
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repins the extension to the SIMAI Framework release
ui-132b0863e12b, the release the owner picked for 0.3.0. The Framework promotes registry entries by its written rule (contracts/owners/PROMOTION.md) and no longer holds the button group.What changed
simai/ui@ef384677, runtimesimai/ui@132b0863(core and smart are the same commit in this release), sizing contract fromsimai/ui-source@6b16b41d. 296 files vendored.sf-list-itemand nowsf-button-groupcomplete on their own; the seven new tokens are the button group's public variables.sf-inline-editor(no declared inputs) andsf-toggle(deprecated in favour ofsf-switch) are not suggested, but stay known, so they are never reported as misspellings. Each held entry now carries its reason inreadiness.blockers.simai/ui-source#10), so thesmart.buttons,smart.icon-buttons,smart.button-groupandsmart.spinnermanifests changed upstream.simai.vertical-sizing@1.3.0, same hash as before.readinessdoes not callready.sf-modal-dialog, now that modal is safe to suggest.npm run screenshotswaits for the suggest widget to hold its rows, lets it settle, then clips to the last row at 2x. No more "Loading…" scenes, half-faded hovers or windows full of empty editor; two runs give the same six sizes.Evidence
npm run generate:checkui-132b0863e12b)npm testnpm run lintnpm run test:extensionnpm run package:checkvsce packagenpm audit --omit=devExpectations from the Framework thread all matched the vendored snapshot: 345 entries, 172 safe (component 61, smart-component 52, utility 58, recipe 1), and the three held ids with exactly the stated
readiness.blockers. Cross-checked againstcontracts/owners/promotion.jsonatef384677: all 136 promoted ids are safe and ready here, plus the 36 curated ids = 172, and all 3 held ids are excluded.Not done here
ui-32c7a64e4575, so their hover panels name the old release. Retaking them needs screen-recording permission on the owner's machine.readiness.blockersis now machine-readable upstream, so that explanation is a follow-up, not part of this repin.🤖 Generated with Claude Code