Skip to content

feat(screenote): create explicitly named projects - #36

Merged
ivankuznetsov merged 1 commit into
mainfrom
fix/screenote-explicit-project-create
Jul 31, 2026
Merged

feat(screenote): create explicitly named projects#36
ivankuznetsov merged 1 commit into
mainfrom
fix/screenote-explicit-project-create

Conversation

@ivankuznetsov

Copy link
Copy Markdown
Owner

Summary

Screenote capture and snapshot flows can now create an exactly named missing project when the user explicitly requests it, instead of stopping with instructions to create it elsewhere. Creation remains guarded against inferred names, ambiguity, duplicate exact matches, and missing_project errors without explicit create intent; successful creation must return the requested project before uploads continue.

The protected release probe now uses the pinned CLI's real page list grammar, so it will no longer fail on unsupported pagination flags. This also prepares the Screenote package surfaces and changelog for 3.1.0.

Validation

  • All 73 repository tests pass, including launcher allowlist, invalid-argument, generated-package, and credential-redaction coverage.
  • The installed Screenote CLI passes the launcher's live non-secret contract check.
  • A live OAuth-authenticated project create created rabata.io and returned project ID 24.
  • The protected integration environment now has the verified project/page/screenshot fixture IDs. Its live job remains intentionally undispatched until a dedicated API key and annotation ID are created through an authenticated Screenote UI session.

@ivankuznetsov
ivankuznetsov merged commit 1e8cf14 into main Jul 31, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant