Skip to content

Prepare for tinycloud 0.3.23: Find Moments — rubric-driven discovery (skill floor → 0.3.23) - #33

Open
kdr wants to merge 1 commit into
mainfrom
prep/0.3.23-find-moments
Open

Prepare for tinycloud 0.3.23: Find Moments — rubric-driven discovery (skill floor → 0.3.23)#33
kdr wants to merge 1 commit into
mainfrom
prep/0.3.23-find-moments

Conversation

@kdr

@kdr kdr commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

tinycloud 0.3.23 (Cloudglue SDK 0.7.29, spec v0.7.23) adds the moments verb — the first new verb since query. Verbs 17→18; features 49→52 (moments.v1, moments.collections.v1, moments.search.v1).

What the skill now teaches

moments sweeps a whole video against a rubric the caller wrote and persists every window that qualifies. That makes it the fourth retrieval shape, and the easiest to reach for by mistake — so the skill leads with the split:

Verb What it does
probe / ask FIND content semantically
extract pull declared fields from known places
search local keyword grep over cached context
moments measure a whole video against a rubric, keeping every hit

Three contracts that are easy to get backwards, each called out explicitly:

  1. --limit/--min-score/--sort shape the READ, not the result. Every accepted moment stays persisted and total_moments reports the full count — re-read with moments show, don't re-run.
  2. --sort criterion-score|rank on a collection requires --criterion <name>. Scores only compare within one rubric.
  3. Detaching a criterion (or removing a file) drops moments from collection enumeration, not from existence. The underlying runs persist as job history.

Also taught: criterion names are lowercase snake_case; a moments collection needs at least one criterion at create; attaching a criterion is free while the per-file backfill runs bill as they execute, so the skill says ask the user before attaching to a large collection; and moments are searched with moments search, not probe --scope moment — probe runs on deep search, which has only file and segment scopes.

Stated as a limit rather than implied away: as of spec v0.7.23 the query verb has no moments virtual tables and ask/responses have no moment awareness, so moments are discoverable and searchable but not yet countable.

Floor raise

tinycloud-skill.json skill_version / min_version / supported_range0.3.23, required_features +moments.v1 +moments.collections.v1 +moments.search.v1, with preflight.sh kept byte-identical.

Plugin + marketplace metadata → 0.3.23 — now enforced automatically by the version-parity check added in #32, rather than by remembering.

Verification

Gate Result
npm test 42 pass / 0 fail
shellcheck clean
CI plugin/skill metadata — all 3 checks locally JSON valid · preflight↔manifest parity (40 features, >=0.3.23 <0.4.0) · frontmatter
Version parity (the new #32 check) every field at 0.3.23

The binary behavior these docs describe was verified live on the paired internal PR: a real find-moments sweep, the moments-collection lifecycle end to end, and the read-time-shaping invariant proven against the API.

…(skill floor → 0.3.23)

tinycloud 0.3.23 (SDK 0.7.29, spec v0.7.23) adds the `moments` verb — the
first new verb since `query` (verbs 17→18, features 49→52: moments.v1,
moments.collections.v1, moments.search.v1).

`moments` sweeps a WHOLE video against a rubric the caller wrote and
persists every window that qualifies, which makes it the fourth retrieval
shape and the easiest to reach for by mistake. The skill teaches the split
explicitly — probe/ask FIND semantically, extract pulls declared fields,
search greps cached context, moments measures against a rubric — plus the
three contracts that are easy to get backwards:

- --limit/--min-score/--sort shape the READ, not the result: every accepted
  moment stays persisted and total_moments reports the full count.
- --sort criterion-score|rank on a collection requires --criterion <name>,
  because scores only compare within one rubric.
- Detaching a criterion (or removing a file) drops moments from collection
  ENUMERATION, not from existence — the runs persist as job history.

Also taught: criterion names are lowercase snake_case; a moments collection
needs at least one criterion at create; attaching a criterion is free while
the per-file backfill runs bill as they execute (so ask before attaching to
a large collection); and moments are searched with `moments search`, not
`probe --scope moment` — probe runs on deep search, which has only file and
segment scopes. As of spec v0.7.23 `query` has no moments tables, which the
docs state rather than implying otherwise.

Floor rises to 0.3.23: tinycloud-skill.json
skill_version/min_version/supported_range → 0.3.23 and required_features
+moments.v1 +moments.collections.v1 +moments.search.v1, with preflight.sh
kept byte-identical. Plugin + marketplace metadata → 0.3.23, now enforced by
the version-parity check added in #32.

Verified: npm test 42/42; shellcheck clean; all three CI plugin/skill
metadata checks pass locally (40 features in sync, range >=0.3.23 <0.4.0,
every version field at 0.3.23).
@kdr
kdr requested a review from amyxst August 22, 2026 04:23
@cursor

cursor Bot commented Aug 22, 2026

Copy link
Copy Markdown

PR Summary

Medium Risk
Raises the skill floor and required feature ids to 0.3.23, so agents on older binaries fail preflight until they upgrade. Docs-only in this repo; no launcher or auth code changes.

Overview
Raises the skill/package floor from 0.3.22 → 0.3.23 so agents can use the new moments verb: sweep a whole video against a caller-written rubric and persist every qualifying window.

The skill now treats moments as a fourth retrieval shape (vs probe/ask, extract, local search). It covers criterion naming, hashed snapshots, read-time --limit/--min-score/--sort (not selection), moments collections (--type moments with a required criterion), attach/detach billing, and moments search instead of probe --scope moment.

tinycloud-skill.json / preflight.sh add moments.v1, moments.collections.v1, and moments.search.v1. Plugin, marketplace, and package.json versions match 0.3.23. Merge is gated on CDN channels.stable = 0.3.23.

Reviewed by Cursor Bugbot for commit 106b6c6. Bugbot is set up for automated code reviews on this repo. Configure here.

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