paces 0.0.11__tar.gz → 0.0.13__tar.gz

{paces-0.0.11 → paces-0.0.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: paces
-Version: 0.0.11
+Version: 0.0.13
 Summary: Turn instructional media into structured, interactive learning material
 Project-URL: Homepage, https://github.com/thorwhalen/paces
 Project-URL: Repository, https://github.com/thorwhalen/paces
@@ -20,8 +20,8 @@ Requires-Dist: argcomplete>=3; extra == 'cli'
 Requires-Dist: cw<0.2,>=0.1.1; extra == 'cli'
 Provides-Extra: dev
 Requires-Dist: cw<0.2,>=0.1.1; extra == 'dev'
-Requires-Dist: lacing>=0.0.40; extra == 'dev'
-Requires-Dist: mixing[audio,beats]>=0.0.39; extra == 'dev'
+Requires-Dist: lacing>=0.0.54; extra == 'dev'
+Requires-Dist: mixing[audio,beats,media]>=0.0.39; extra == 'dev'
 Requires-Dist: numba>=0.59; extra == 'dev'
 Requires-Dist: pytest-cov>=4.0; extra == 'dev'
 Requires-Dist: pytest>=7.0; extra == 'dev'
@@ -31,9 +31,9 @@ Provides-Extra: docs
 Requires-Dist: sphinx-rtd-theme>=1.0; extra == 'docs'
 Requires-Dist: sphinx>=6.0; extra == 'docs'
 Provides-Extra: lacing
-Requires-Dist: lacing>=0.0.40; extra == 'lacing'
+Requires-Dist: lacing>=0.0.54; extra == 'lacing'
 Provides-Extra: media
-Requires-Dist: mixing>=0.0.39; extra == 'media'
+Requires-Dist: mixing[media]>=0.0.39; extra == 'media'
 Provides-Extra: pose
 Requires-Dist: onnxruntime; extra == 'pose'
 Requires-Dist: rtmlib<0.1,>=0.0.16; extra == 'pose'

{paces-0.0.11 → paces-0.0.13}/docs/README.md

@@ -13,7 +13,7 @@ a dance, plus a hand-written HTML aide-mémoire, plus a paragraph of steering pr
 deployed interactive practice page: <https://thorwhalen.com/que_calor_dance/>.
 
 The user now wants that generalised into a library, integrated with the **reelee** /
-`video_gen` fleet. Your job is to research, design and build it. **This folder exists so you
+`av` (formerly `video_gen`) fleet. Your job is to research, design and build it. **This folder exists so you
 do not start from scratch.** It records what was built, the parameters that were expensive to
 find, the failures and what each one teaches, the user's own framing of the generalisation,
 and an inventory of what already exists in the fleet.
@@ -28,7 +28,7 @@ Nothing here is a design you must follow. It is evidence and framing. Argue with
 | 2 | **`03-design-brief.md`** | The user's own framing: the parse→AST→render metaphor they explicitly asked to have recorded, the three generalisation axes, and the constraints the POC discovered. |
 | 3 | **`04-reelee-core.md`** | What reelee is, what a reelee "genre" is, and what to reuse. **This determines the package boundary**, so read it before deciding anything structural. |
 | 4 | **`07-annotation-model.md`** | The proposed shape of the AST — the contract between analysis and rendering. |
-| 5 | **`05-fleet-inventory.md`** | What already exists across `video_gen`, and honestly which parts are stubs. |
+| 5 | **`05-fleet-inventory.md`** | What already exists across `av`, and honestly which parts are stubs. |
 | 6 | **`02-technical-recipes.md`** | Every technique with working parameters. Reference, not narrative — come back to it when implementing. |
 | 7 | **`06-surfaces-and-conventions.md`** | House style: architecture-first seams, qh, py2mcp, storage, frontend, deploy. |
 | 8 | **`08-naming-candidates.md`** | PyPI-verified name options, and a better word for the "subject" axis. |
@@ -37,7 +37,7 @@ Nothing here is a design you must follow. It is evidence and framing. Argue with
 | — | **`adr/`** | The decisions. **`0003` `video + segmenter`** — read it before designing the analysis phase. `0002` the name. `0001` the alignment engine (intent) — note that much of what you'd otherwise build already exists in `muvid`, `mixing` and `kodokan`. |
 | — | **`alignment/`** | The research behind that ADR: one file per method family, prepared so you don't start from a literature search. |
 | — | **`KICKOFF.md`** | A paste-ready prompt to start a fresh session on this. |
-| — | **`REGISTRATION.md`** | **One command still pending** to register `paces` in the `video_gen` group, and why `priv pkg add-package` is deliberately deferred. |
+| — | **`REGISTRATION.md`** | **One command still pending** to register `paces` in the `av` group, and why `priv pkg add-package` is deliberately deferred. |
 | — | **`poc-reference/`** | The actual scripts and data. Read `poc-reference/README.md` first — several of those files are recorded dead ends. |
 
 ## The one-paragraph version

{paces-0.0.11 → paces-0.0.13}/docs/alignment/README.md

@@ -1,7 +1,7 @@
 # Alignment research
 
 *What this folder is for: preparation for a possible dedicated **alignment tool** in the
-`video_gen` / reelee fleet — the thing that answers "given some artifacts and some media,
+`av` (formerly `video_gen`) / reelee fleet — the thing that answers "given some artifacts and some media,
 which span of the media does each artifact correspond to?". The decision to build it is
 recorded as an intent in `../adr/0001-alignment-engine-as-a-fleet-package.md`; **read that
 first**, then come here for the method-by-method detail.*

{paces-0.0.11 → paces-0.0.13}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "paces"
-version = "0.0.11"
+version = "0.0.13"
 description = "Turn instructional media into structured, interactive learning material"
 readme = "README.md"
 license = "MIT"
@@ -57,7 +57,7 @@ media = [
     # all run on the pip-bundled imageio-ffmpeg binary — no system ffmpeg.
     # Floor 0.0.39: make_gif, crop_box= and path-accepting
     # get_video_dimensions ship there.
-    "mixing>=0.0.39",
+    "mixing[media]>=0.0.39",
 ]
 # The pointable subject_locator (issue #15, ADR-0005 §3): rtmlib pose boxes,
 # reached through `paces.pose:rtmlib_pose`. rtmlib is Apache-2.0 (a pure-Python
@@ -107,7 +107,7 @@ pose = [
 # unknown keys — both of which this layer's round trip relies on to fail loudly
 # instead of silently normalising.
 lacing = [
-    "lacing>=0.0.40",
+    "lacing>=0.0.54",
 ]
 dev = [
     "pytest>=7.0",
@@ -120,11 +120,11 @@ dev = [
     # synthesized audio; mirrored with [audio] so they run rather than skip.
     # The derivation tests do the same on synthetic video — mirrored with
     # [media] (the >=0.0.39 floor wins over [audio]'s >=0.0.36).
-    "mixing[beats,audio]>=0.0.39",
+    "mixing[beats,audio,media]>=0.0.39",
     "numba>=0.59",
     # The evidence-layer tests run against real, dict-backed lacing stores —
     # mirrored with [lacing] so they run rather than skip.
-    "lacing>=0.0.40",
+    "lacing>=0.0.54",
     # tests/test_pose.py reads pyproject.toml to guard the licence perimeter;
     # stdlib tomllib is 3.11+, and a skipped guard guards nothing.
     "tomli>=2.0; python_version < '3.11'",

{paces-0.0.11 → paces-0.0.13}/tests/data/body_schemas.json

@@ -27,6 +27,7 @@
       },
       "attrs": {
         "additionalProperties": true,
+        "default": {},
         "description": "Open bag.",
         "title": "Attrs",
         "type": "object"
@@ -146,6 +147,7 @@
     "properties": {
       "attrs": {
         "additionalProperties": true,
+        "default": {},
         "description": "Namespaced open bag, as on the document.",
         "title": "Attrs",
         "type": "object"
@@ -175,6 +177,7 @@
         "type": "string"
       },
       "flags": {
+        "default": [],
         "description": "The run's honesty flags (``Segmentation.flags``) — 'naming-abstained', 'origin-estimated: ...', and friends. Evidence about the run, never projected into the document.",
         "items": {
           "type": "string"
@@ -389,6 +392,7 @@
           "pattern": "^-?\\d+(\\.\\d+)?$",
           "type": "string"
         },
+        "default": {},
         "description": "Policy parameters the box was resolved under (aspect, pad). A change here re-locates an unlocked entry.",
         "title": "Params",
         "type": "object"
@@ -460,6 +464,7 @@
       },
       "attrs": {
         "additionalProperties": true,
+        "default": {},
         "description": "Open bag.",
         "title": "Attrs",
         "type": "object"
@@ -546,6 +551,7 @@
     "properties": {
       "attrs": {
         "additionalProperties": true,
+        "default": {},
         "description": "Namespaced open bag, as on the step.",
         "title": "Attrs",
         "type": "object"
@@ -610,6 +616,7 @@
       },
       "span_attrs": {
         "additionalProperties": true,
+        "default": {},
         "description": "Open bag on the span.",
         "title": "Span Attrs",
         "type": "object"
@@ -712,6 +719,7 @@
         "type": "string"
       },
       "tags": {
+        "default": [],
         "description": "Open tag vocabulary.",
         "items": {
           "type": "string"

{paces-0.0.11 → paces-0.0.13}/tests/test_evidence_schemas.py

@@ -12,6 +12,12 @@ halves of that claim:
   migration; a *changed* one is a wire break for every already-written store,
   and this test is what makes that a decision rather than an accident.
 
+Annotation-only keywords a lacing upgrade starts exporting (``default``,
+``description``) may be re-snapshotted — they validate nothing, so no stored
+body changes meaning (lacing 0.0.54 added the ``default_factory`` defaults;
+the floor in pyproject follows). A change to a field, type or ``required`` is
+the wire break and needs ``/v2``.
+
 Regenerating the snapshot deliberately::
 
     python -m tests.test_evidence_schemas   # writes tests/data/body_schemas.json