terp-cli 0.5.1__tar.gz → 0.5.2__tar.gz

terp_cli-0.5.2/PKG-INFO

@@ -0,0 +1,16 @@
+Metadata-Version: 2.4
+Name: terp-cli
+Version: 0.5.2
+Summary: Terp command-line tool — inspect, scaffolding, migrations, checks, api-docs.
+License-Expression: Apache-2.0
+Requires-Python: >=3.13
+Requires-Dist: terp-arch==0.5.2
+Requires-Dist: terp-core==0.5.2
+Requires-Dist: terp-migrations==0.5.2
+Provides-Extra: jobs
+Requires-Dist: terp-cap-outbox==0.5.2; extra == 'jobs'
+Requires-Dist: terp-cap-scheduler-apscheduler==0.5.2; extra == 'jobs'
+Provides-Extra: scheduler
+Requires-Dist: terp-cap-scheduler-apscheduler==0.5.2; extra == 'scheduler'
+Provides-Extra: worker
+Requires-Dist: terp-cap-outbox==0.5.2; extra == 'worker'

{terp_cli-0.5.1 → terp_cli-0.5.2}/pyproject.toml

@@ -4,29 +4,29 @@ build-backend = "hatchling.build"
 
 [project]
 name = "terp-cli"
-version = "0.5.1"
+version = "0.5.2"
 description = "Terp command-line tool — inspect, scaffolding, migrations, checks, api-docs."
 requires-python = ">=3.13"
 license = "Apache-2.0"
 dependencies = [
-    "terp-core==0.5.1",
+    "terp-core==0.5.2",
     # `terp migrate` delegates to terp-migrations (lazily imported), keeping Alembic
     # off the path for `terp inspect` / `terp guide` while making migrations work.
-    "terp-migrations==0.5.1",
+    "terp-migrations==0.5.2",
     # `terp guide rules` projects the live rule registry; terp-arch is imported lazily
     # (only when that topic is rendered), so it stays off the common `terp guide` path.
-    "terp-arch==0.5.1",
+    "terp-arch==0.5.2",
 ]
 
 # Job-process adapters stay optional: the base CLI must not install the table-owning outbox
 # or a scheduler engine into apps that only use inspect/check/migrate. Deployments can select
 # one process role, while `jobs` is the convenient complete jobs-process bundle.
 [project.optional-dependencies]
-worker = ["terp-cap-outbox==0.5.1"]
-scheduler = ["terp-cap-scheduler-apscheduler==0.5.1"]
+worker = ["terp-cap-outbox==0.5.2"]
+scheduler = ["terp-cap-scheduler-apscheduler==0.5.2"]
 jobs = [
-    "terp-cap-outbox==0.5.1",
-    "terp-cap-scheduler-apscheduler==0.5.1",
+    "terp-cap-outbox==0.5.2",
+    "terp-cap-scheduler-apscheduler==0.5.2",
 ]
 
 [project.scripts]

{terp_cli-0.5.1 → terp_cli-0.5.2}/src/terp/cli/__init__.py

@@ -337,15 +337,60 @@ Password strength (PasswordPolicy, Tier-B)
     "events": """\
 Domain events (eventbus capability)
 
+- The capability is a separate distribution — nothing below exists until you add it:
+      uv add terp-cap-eventbus
+  Then import from terp.capabilities.eventbus (EventEmittingService, LifecycleEventMap,
+  subscribe, dispatch_in_process).
 - Declare typed events in your control plane (never bare strings):
       NOTE_CREATED = EventDefinition("note.created", payload_schema=NoteCreatedPayload)
       event_catalog = EventCatalog([NOTE_CREATED])
+- Declare what the module produces in its manifest. The emits list is the module's
+  published contract, so the gate refuses an event you emit without naming it here:
+      module = ModuleSpec(name="notes", emits=[NOTE_CREATED, NOTE_ARCHIVED])
 - Emit declaratively from a service (atomic with the write):
       class NoteService(EventEmittingService[Note, NoteCreate, NoteUpdate]):
           model = Note
           event_map = LifecycleEventMap(created=NOTE_CREATED)
+- The map covers "every write of this shape emits this event". When the decision is
+  CONDITIONAL — a state transition, one event for some updates and none for others —
+  extend the same hook rather than emitting from a router or a task:
+      class NoteService(EventEmittingService[Note, NoteCreate, NoteUpdate]):
+          model = Note
+          event_map = LifecycleEventMap(created=NOTE_CREATED)
+
+          def _after_write(self, session, entity, action) -> None:
+              super()._after_write(session, entity, action)
+              if action is AuditAction.UPDATED and entity.status == "archived":
+                  emit(session, event=NOTE_ARCHIVED, payload=NoteArchivedPayload(id=entity.id))
+  _after_write runs inside the write's transaction, so a conditional emit is still
+  atomic with the row it describes — which is the whole reason the map lives there.
 - Subscribe with @subscribe(NOTE_CREATED). Reference catalog constants only (the gate
   enforces no-drift). Wire create_app(..., event_dispatcher=dispatch_in_process).
+- Switching the bus on in a service-level test: the `terp_events` fixture, never a
+  direct configure_events (see `terp guide testing`).
+""",
+    "testing": """\
+Testing a Terp app (process-global runtime isolation)
+
+- create_app installs SIX process globals per app: the audit policy+sink, the event
+  catalog+dispatcher, the job catalog+queue, the schedule catalog, the password policy,
+  and the decrypt call site. In a test process they outlive the app that installed them.
+- You get isolation for free. terp-core ships a pytest plugin (terp.core.testing,
+  registered under pytest11) whose autouse fixture SNAPSHOTS every runtime before a
+  test and RESTORES it after. No conftest.py line, no opt-in. Without it a suite goes
+  order-dependent: green together, red alone - the sharpest failure mode there is,
+  because the green is the wrong answer.
+- Isolation does not INSTALL a runtime your test needs - that is your decision:
+      * whole runtime -> compose the app in a fixture (see apps/example/tests/conftest.py,
+        where db_engine + app_db are function-scoped and build() runs per test)
+      * only the event bus -> the `terp_events` fixture, which installs a catalog
+        (and dispatcher) for the duration of one test:
+            terp_events(event_catalog, dispatcher=dispatch_in_process)
+      * asserting on what was written to a FAKE/bare session -> `terp_default_runtime`,
+        which states the baseline instead of assuming it. Without it a composed app's
+        durable audit sink quietly adds audit rows to the session under assertion.
+- If a test passes in the suite and fails alone (or vice versa), it is reading a
+  runtime it never installed. Install it explicitly; never re-order the suite.
 """,
     "jobs": """\
 Background jobs (terp.core.enqueue + JobCatalog)

terp_cli-0.5.1/PKG-INFO

@@ -1,16 +0,0 @@
-Metadata-Version: 2.4
-Name: terp-cli
-Version: 0.5.1
-Summary: Terp command-line tool — inspect, scaffolding, migrations, checks, api-docs.
-License-Expression: Apache-2.0
-Requires-Python: >=3.13
-Requires-Dist: terp-arch==0.5.1
-Requires-Dist: terp-core==0.5.1
-Requires-Dist: terp-migrations==0.5.1
-Provides-Extra: jobs
-Requires-Dist: terp-cap-outbox==0.5.1; extra == 'jobs'
-Requires-Dist: terp-cap-scheduler-apscheduler==0.5.1; extra == 'jobs'
-Provides-Extra: scheduler
-Requires-Dist: terp-cap-scheduler-apscheduler==0.5.1; extra == 'scheduler'
-Provides-Extra: worker
-Requires-Dist: terp-cap-outbox==0.5.1; extra == 'worker'