simcord 3.2.0__tar.gz → 3.2.1__tar.gz

{simcord-3.2.0 → simcord-3.2.1}/.github/workflows/verify.yml

@@ -11,6 +11,12 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci --ignore-scripts
+      - run: npm run check:preview
       - uses: astral-sh/setup-uv@v7
       # screenshot extra pulls in playwright/PIL/markdown-it so pyright resolves
       # the lazy optional imports in simcord.preview with real type info.

{simcord-3.2.0 → simcord-3.2.1}/.gitignore

@@ -15,6 +15,9 @@ build/
 .hypothesis/
 .coverage
 htmlcov/
+node_modules/
+npm-debug.log*
+*.tsbuildinfo
 
 # Editors
 .idea/

{simcord-3.2.0 → simcord-3.2.1}/CHANGELOG.md

@@ -4,6 +4,25 @@ This changelog is generated with [towncrier](https://towncrier.readthedocs.io/).
 
 <!-- towncrier release notes start -->
 
+## 3.2.1 (2026-10-24)
+
+### Bug fixes
+
+- Fix obsolete preview responses restoring an older viewer, and reauthorize cached references, identities, command catalogs, and retained autocomplete results without publishing unrelated edits. Centralize browser read/poll ownership and capture geometry; release evicted media, clear private modal and command-picker state, preserve native keyboard focus, and make simulated layouts follow their logical viewport. Preserve affected-message diagnostic navigation and terminal completeness across Inspector redraws; recover cached catalogs even when an obsolete read fails. Keep protocol 3 and status schema 1 unchanged; add development-only checks for the extracted JavaScript boundaries.
+
+  Give browser actions, assets, catalog observations, File-bearing drafts and rendered surfaces explicit lifetimes; strictly check all first-party JavaScript and preserve frozen publication/result provenance across revocation and capture. Validate compound member/voice and forum mutations before committing state, enforce actor and bot REST authority without conflating token access, and track actual executor execution separately from caller cancellation. Split capture configuration, journal/recovery and transport responsibilities; independently verify exact API test-grant provenance and retain distinct capture crop policies. Networked reference capture now requires aiohttp 3.12+ to prevent implicit uncertain-write retries; Preview library requirements are unchanged.
+
+  Preserve supported native SDK overwrite targets while rejecting foreign state and cross-guild roles/members; apply existing-emoji reaction permissions consistently in actors, REST and preview controls. Keep newer Reply intents when older sends settle, reconcile refreshed entity selections, and restore Escape after applying modal choices. Verify captured animation content and timing without depending on unrelated avatar antialiasing.
+
+  Move selection-state reporting into its owner, leaving the bootstrap to assemble read-only status.
+
+  Observe native executor submission and completion independently of failed or cancelled caller facades, including initializer rejection and picklable process-pool calls. Preserve live gateway, shard and webhook machinery after a native-work shutdown timeout. Keep deleted session-owned grants out of later baselines without weakening receipt checks. Preserve earlier bot avatars when a human DM message is focused or captured, while retaining live revocation checks; construct uncached SDK messages with native partial channels.
+
+  Release successful executor callables without retaining them until long-lived parent tasks finish; preserve unobserved-error handling.
+
+  Reject DM and cross-guild service-message references at the fixture boundary while preserving valid same-guild, cross-channel references. ([#41](https://github.com/SilentHacks/simcord/pull/41))
+
+
 ## 3.2.0 (2026-10-22)
 
 ### Features

{simcord-3.2.0 → simcord-3.2.1}/CONTRIBUTING.md

@@ -16,8 +16,9 @@ uv run ruff check src tests examples benchmarks scripts && uv run ruff format --
 uv run pyright src
 ```
 
-The pre-commit hooks mirror the CI `lint` job (ruff on commit, pyright on push)
-using the project's own pinned tools, so a clean commit means a green CI lint.
+The Python hooks run ruff on commit and pyright on push using the project's
+pinned tools. Run the frontend check below separately; passing Python hooks
+does not replace the JavaScript CI gate.
 
 Optional extras layer on top of `dev` depending on what you work on:
 
@@ -31,6 +32,19 @@ uv sync --extra dev --extra screenshot                # matches the CI lint job
 uv run playwright install --with-deps chromium        # needed once for browser capture tests + the example
 ```
 
+Frontend contributors also need Node 24:
+
+```bash
+npm ci --ignore-scripts
+npm run check:preview
+```
+
+This strict JSDoc check includes every first-party `static/*.js` module and the
+composing callers. The explicit root glob and `noResolve` keep unchanged vendored
+Highlight.js code behind narrow declarations, not behind disabled first-party
+checks. New first-party modules belong in that checked root and the server's
+static allowlist. Preview users and installed-wheel captures do not need Node.
+
 ## Project layout
 
 - `src/simcord/backend/`: the virtual Discord with dataclass models, wire-format
@@ -42,6 +56,18 @@ uv run playwright install --with-deps chromium        # needed once for browser
 - `src/simcord/{env,builders,actors,results,interactions}.py`: the public API.
 - `src/simcord/_dpy_internals.py`: **every** touch of a private discord.py API,
   behind an import-time self-check. New private-API usage goes here, nowhere else.
+- `src/simcord/_runtime.py`: paired loop hooks and owned task/callback/executor
+  bookkeeping; `_settlement.py` consumes a narrow settlement view, not the world.
+- `src/simcord/preview/static/app.js`: page composition and event wiring.
+  `actions.js` owns POST admission; `session.js` owns state reads/polling;
+  `assets.js` owns shared URLs and derived metadata. Composer, select, modal,
+  timeline and workbench owners keep their own mutable feature state.
+- `command-catalog.js` owns catalog observations, `command-drafts.js` owns
+  versioned File-bearing drafts, and `commands.js` owns the native picker view.
+- `scripts/monetization_reference_{config,journal,transport}.py`: validated
+  capture-mode configuration, durable ownership/recovery and raw transport.
+  `validate_monetization_reference.py` independently verifies evidence in explicit
+  phases; recorder flags alone are not authorization.
 
 ## Guidelines
 

{simcord-3.2.0 → simcord-3.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: simcord
-Version: 3.2.0
+Version: 3.2.1
 Summary: Offline discord.py bot testing with pytest. No network, token, or test server.
 Project-URL: Homepage, https://github.com/SilentHacks/simcord
 Project-URL: Documentation, https://simcord.readthedocs.io/

{simcord-3.2.0 → simcord-3.2.1}/docs/architecture.md

@@ -63,10 +63,17 @@ test ──► builders/actors ──► virtual backend (single source of truth
   discord.py's master branch to catch drift early.
 - **Deterministic snowflakes** with valid embedded timestamps, from a fixed virtual epoch.
 
-`Env` remains the lifecycle and state owner. Private runtime hooks live in `_runtime.py`;
-`_settlement.py` classifies tracked work and manages virtual timer bookkeeping against that
-same state. `_modal.py` handles modal validation and serialization through the existing actor
-permission checks and interaction dispatch.
+`Env` remains the lifecycle and world owner. `_runtime.py` pairs hook installation
+with restoration and owns task, callback, executor and external-wait records.
+`_settlement.py` classifies those records through a narrow settlement view.
+Executor completion is separate from cancellation of the caller's Future;
+paired hooks observe actual owned standard-library pool submissions and are
+restored after the last Env detaches.
+`_modal.py` handles modal validation and serialization through the existing actor
+permission checks and interaction dispatch. Backend/ID access facts are shared
+below Env-bound viewer adapters; bot, human, fixture and token authority remain
+distinct. Compound Backend mutations validate all inputs before committing model
+state and gateway events; HTTP routes retain caller, reason and audit context.
 
 ## Optional browser presentation
 
@@ -83,10 +90,31 @@ Optional Pillow media work is bounded and outside Env's loop. Optional Playwrigh
 settled projection and reports geometry, readiness, completeness, calibration, and diagnostics.
 Base imports do not allocate any preview server, worker, or browser.
 
-Preview keeps session/page state in its existing owners. `_action_plans.py` prepares lazy
-actions; identity, component/message projection, and query modules feed `_snapshot.py`'s
-assembly. In the browser, `app.js` retains shared state and action sequencing, with focused
-workbench, select-draft, timeline, and transport modules handling presentation responsibilities.
+Preview keeps session/page state in its existing owners. `_action_plans.py` prepares
+lazy actions; identity, component/message projection and query modules feed
+`_snapshot.py`'s assembly. Publications and the latest retained result each keep
+their own frozen dependencies. Request-local authorization removes lost dependencies
+without publishing unrelated edits. Capture pins check actual dependency loss before
+and after PNG creation, not arbitrary differences between serialized snapshots.
+
+In the browser, `app.js` composes owners and wires events. `actions.js` sequences
+admitted POSTs, including browse/autocomplete; `session.js` owns validated state reads,
+checkpoints, cancellation and polling. Catalog observations and versioned File-bearing
+drafts have separate owners from the native command-picker view. `assets.js` owns
+shared URLs and derived metadata without mutating published manifests; rendered
+surfaces own DOM/player disposal. Composer, select, modal, timeline, diagnostics,
+presentation and workbench records retain their focused responsibilities. Status is
+assembled from read-only owner reports, with protocol 3 and schema 1 unchanged.
+
+`geometry.js` supplies live status and capture measurements. Managed captures round
+inside their visible intersection; complete control/menu captures round outward and
+reject off-host bounds. These intentionally different policies share measurement
+primitives, not forced identical crops. Python and browser diagnostics share the
+packaged vocabulary. These remain native ES modules, without a bundler or framework.
+
+Contributor checks use Node 24: `npm ci --ignore-scripts` and `npm run check:preview`
+strictly check every first-party JavaScript module and its composing callers.
+Python consumers and installed-wheel captures do not need Node.
 
 ## What it will never do
 

{simcord-3.2.0 → simcord-3.2.1}/docs/guides/monetization.md

@@ -251,6 +251,13 @@ and Send Messages permissions, and one text channel named `parity`. Leave
 privileged intents disabled and the Interactions Endpoint URL blank. Do not run
 alongside another process using the same bot.
 
+Networked reference capture requires **aiohttp 3.12+** for its public per-request
+middleware API. This prevents aiohttp from silently retrying uncertain writes,
+including DELETE/PUT; only explicitly recorded HTTP 429 retries remain enabled.
+The recorder checks this prerequisite before requesting credentials or recording
+a mutation intent. Preview's library dependency remains `aiohttp>=3.9`; offline
+evidence validation does not need the capture transport.
+
 From the repository root, run in your own interactive terminal:
 
 ```bash
@@ -409,6 +416,11 @@ It does **not** turn captured facts into simulator calibration approval.
 inspect the named blocked cases and reasons in `manifest.json`. A completed run
 does not prove all lifecycle cases or fix simulator behavior.
 
+Validation is independent of recorder ownership flags. API test-create proof needs
+an exact integer type 8, the requested application/SKU/owner and a fresh,
+non-manual ID. Explicitly authorized manual type-4 purchases use a separate proof
+path. Malformed evidence produces located error codes without echoing raw values.
+
 The validator can also run without credentials:
 
 ```bash
@@ -436,6 +448,18 @@ uv run python scripts/capture_remaining_monetization.py \
   --resume CAPTURE_DIRECTORY --cleanup-only
 ```
 
+Cleanup-only loads the saved identities and verifies correlated positive receipts;
+it does not require a new capture's checkout configuration or source fixtures.
+Recovery preserves schema-1 ordered correlation and schema-2 request IDs. A
+success-looking manifest flag or an earlier retry response cannot establish ownership.
+
+Deleted sandbox grants remain session-owned history, backed by their original
+positive receipts. Later baseline scans do not adopt those IDs as pre-existing
+resources, so repeated resume and cleanup-only remain safe. A journal that
+already lists the same ID as both baseline and owned is still rejected; resolve
+that conflict by auditing its evidence, not by discarding history or weakening
+the ownership check.
+
 Recovery cannot change the original app/server/owner identities. A second owner
 may be added to a run that previously lacked one; the relevant comparison
 sections are reopened, not the purchase batches. Connection gaps and interrupted

{simcord-3.2.0 → simcord-3.2.1}/docs/guides/permissions.md

@@ -38,8 +38,10 @@ locked = guild.create_text_channel(
 )
 ```
 
-Overwrite targets can be roles (`guild.default_role`, any `RoleHandle`) or members
-(`MemberActor`).
+Overwrite targets can be `RoleHandle`, `MemberActor` or `UserHandle` objects, or native
+`discord.Role`, `discord.Member`, `discord.User` and `discord.ClientUser` objects from the
+same Env's SDK state. Roles and members must belong to the target guild. Foreign SDK
+state and cross-guild role/member targets are rejected before channel creation.
 
 !!! info "The bot's default permissions"
     By default the bot gets a managed integration role with broad permissions but **not**
@@ -59,6 +61,8 @@ Overwrite targets can be roles (`guild.default_role`, any `RoleHandle`) or membe
   (`50013`). It also can't delete the `@everyone` role.
 - **Editing others' messages** — the bot can't edit another user's message (`50005`).
 - **Timeouts** — a timed-out member loses everything except viewing and reading history.
+- **Reactions** — `add_reactions` is required to introduce a new emoji, not to join an
+  existing reaction. Both require access to the message and its history.
 
 ```python
 async def test_cannot_ban_higher_role(simcord_env):

{simcord-3.2.0 → simcord-3.2.1}/docs/guides/preview.md

@@ -133,6 +133,9 @@ its original opener; the source-message linkage remains available to `interactio
   authorized independently. A denied target is not distinguished from a missing target.
 - Access is rechecked on every state, asset, and pinned-capture read. Revoked access or removed
   attachments invalidate cached content; already delivered pixels cannot be remotely recalled.
+  Security redaction can remove already-published references, summaries, identities, candidates,
+  command entries, and asset handles without advancing the revision. It never publishes unrelated
+  edits or newly granted content. A pinned capture fails closed if a published dependency loses access.
 
 The capability holder may switch between supplied viewers. It is not authentication for unrelated
 humans; use separate sessions for separate trust domains. Treat `preview.url`, terminal output,
@@ -141,9 +144,9 @@ logs, reports, bug issues, or screenshots.
 
 ## Refresh and staleness
 
-Preview uses HTTP commands and polling, not a websocket or always-running Python poller. Polling only
-reads the latest published revision. Python actor calls, `advance_time()`, background callbacks, and
-other scenario mutations become visible after an explicit refresh:
+Preview uses HTTP commands and polling, not a websocket or always-running Python poller. Polling
+reads the latest published projection, with current access filtering. Python actor calls,
+`advance_time()`, background callbacks, and other scenario mutations become visible after an explicit refresh:
 
 ```python
 await actor.click(message, custom_id="save")
@@ -161,6 +164,16 @@ cursors. `targetId` identifies the focused projection; there is no `selected` al
 timed-out action may already have mutated the backend: its last settled projection is retained and
 marked stale, then a later successful refresh reconciles it without replaying the action.
 
+The browser coalesces state reads and rejects responses from obsolete request lifetimes or older
+context, bot, or publication checkpoints before changing the UI. A transient read failure retains
+the last authorized projection with a transport warning; HTTP 401/410 or incompatible protocol
+terminates the page and clears private surfaces. Back/forward-cache suspension pauses polling;
+restoration resumes one polling chain. Non-restorable page hides send a best-effort authenticated
+release; browser unload never deletes a restorable context. The existing lease covers undeliverable
+releases, and an expired page requires an explicit reload.
+Back/forward caching depends on browser policy: Preview keeps its `no-store` security headers.
+Navigation that reloads the document does not retain page-local drafts.
+
 ## Controls, keyboard, and accessibility
 
 The bundled page uses semantic HTML buttons, inputs, textareas, native checkboxes/radios/file
@@ -517,6 +530,11 @@ settled projection, DOM, fonts, authorized media, validated display dimensions (
 and two animation frames are ready, with no action or page intent still pending. In particular,
 resize/profile reconfiguration must finish before capture tooling treats the surface as ready.
 It does not mean the callback succeeded, the output is complete, or the capture is calibrated.
+A clean, acknowledged Close can be complete while not render-ready; terminal transport failures
+remain incomplete, and an unaccounted-for action remains uncertain. Inspector filters do not change
+these lifecycle outcomes.
+A matching late Close acknowledgement can confirm closure after a terminal read, without restoring
+the cleared private projection.
 `publishedRevision` is a settled publication;
 `contextGeneration` changes on viewer or focus changes;
 `botGeneration` changes on restart; render generations also cover local changes such
@@ -525,6 +543,10 @@ and premium-icon loads stay bound to retained DOM owners across redraws; replaci
 discards its continuation. A retained owner's late failure still makes the surface incomplete.
 Switching viewers or restarting the bot invalidates asset ownership and recreates media rather than
 carrying playback or pending loads across authorization boundaries.
+Command browsing, composed-command, and entity-suggestion avatars all participate in readiness.
+Replacing or closing a picker releases only its obsolete pending work. Evicting a rendered surface
+pauses and releases its media; retained surfaces keep their pending work. The reported active control
+follows actual browser focus, including individual descendants within a compound control.
 
 `projectedMessageIds` mirrors `snapshot["timeline"]`; `visibleMessageIds` lists only IDs currently
 visible in the simulated viewport, not every projected window item. `geometry` reports measured app,
@@ -545,9 +567,12 @@ correctly typed but stale context or generation values return `stale-context` or
 Kind, control resolution, and values are validated before the sequence is admitted. Admission is
 at-most-once: a duplicate latest request with the same payload returns its recorded outcome, a
 changed payload conflicts, old sequences expire, and gaps are rejected. Busy, stale, unauthorized,
-disabled, deleted, or invalid controls are rejected before admission and are never automatically
-retried. A disconnected client does not cancel an admitted callback; delivery failure is separate
-from callback settlement.
+disabled, deleted, or invalid callbacks are rejected before admission and are never automatically
+retried. Only the latest read-like query intent rejected definitively as busy is reconsidered,
+at most once per successful existing polling tick; this does not replay an admitted or uncertain
+callback. Page intents such as Close and viewer/focus changes queue behind the current action,
+not behind an unreachable publication revision. A disconnected client does not cancel an admitted
+callback; delivery failure is separate from callback settlement.
 
 Revision-bound actions (`click`, `select`, `modal_submit`, `autocomplete_command`, `run_command`,
 `history`, `send_message`, `edit_message`, `delete_message`, `set_reaction`, `set_poll_votes`,
@@ -565,8 +590,10 @@ focuses an authorized outcome, and Back returns to the prior target and invoking
 exists. Receipts never auto-focus a page. A pre-admission rejection does not consume the sequence;
 the activity ledger holds at most 20 receipts and no message bodies, and references are reauthorized
 on every read. Diagnostics use catalog-owned codes and remediation, never raw request or exception
-text. Inspect the receipt and refresh after failures; never retry a consumed sequence to make a
-screenshot look successful.
+text. Validated diagnostic subjects retain affected-message navigation in the private UI, but are
+excluded from safe support reports. Inspect the receipt and refresh after failures; never retry a
+consumed sequence to make a screenshot look successful. Replayed query results that are no longer
+available are omitted; candidate descriptors never become an undocumented null variant.
 Actor dispatch is recorded at the successful backend mutation, before settlement. A later timeout
 or cancellation reports a dispatched, uncertain operation; refreshing and replaying its receipt
 must not repeat the mutation. Denied reads clear channel topics, history boundaries and send capability,
@@ -641,8 +668,12 @@ The full catalog is a separate read, rather than repeated in every state snapsho
 `truncated`, `application` (`id`, `name`, `avatarAssetId`) and `entries`. Each entry describes a
 visible command leaf with its ID, invocation path, scope, schema fingerprint and typed options. The
 schema defines this wire shape at `$defs.commandCatalog`. The response is protected by the page
-capability and context. Catalogs are capped at 1,000 leaves and 2 MiB; an oversized catalog is marked
-`truncated`.
+capability and context, and current command access and schema are checked before cached entries
+are returned. Catalogs are capped at 1,000 leaves and 2 MiB; an oversized catalog is marked `truncated`.
+If the manifest changes while a catalog read is pending, the browser installs only the desired
+catalog and fetches its replacement rather than remaining stuck with a discarded response.
+Returning to an already installed catalog restores it without another fetch; obsolete responses
+and failures cannot displace it.
 
 The two additional revision-bound action kinds are `autocomplete_command` and `run_command`. Both
 carry `command_id`, `path` and `schema_fingerprint`; autocomplete also carries `focused`, `value` and
@@ -651,6 +682,15 @@ parts named `file:<optionName>` rather than JSON bytes. Every receipt has a null
 beside `target`: when present it is `{commandId, invocation}`. The diagnostic subject union adds
 `{commandOption}` beside the existing `{messageId, controlKey?}` form.
 
+`GET /api/action-result?request_id=<id>&sequence=<positive integer>` recovers the original
+autocomplete response after delivery loss without invoking the callback again. It uses the same
+capability/context headers and only the existing latest retained action result, not an action
+history. Recovery requires the original viewer, context and bot generation, command identity,
+schema, and current command/channel access. A matching settled result returns HTTP 200 with the
+existing action response; pending returns 409, unavailable/superseded/scope-changed returns 404,
+expired context returns 410, and missing authorization returns 401. An unavailable result leaves
+the draft intact and reports failure instead of silently resubmitting or loading indefinitely.
+
 Command diagnostics include `commands-unsynced` (call `await bot.tree.sync()`), `command-unavailable`,
 `command-changed`, `command-option-invalid` and `autocomplete-unanswered`. A
 `command-option-invalid` diagnostic identifies the relevant option without exposing raw request or bot
@@ -768,6 +808,11 @@ logical preview viewport, including its modal backdrop and dialog but excluding
 Use an interactive browser session to inspect modal content at both scroll extremes. Width and height
 are positive bounded integers and are checked against the screenshot raster limits above.
 
+Captures pin the presentation profile and requested media time, but native browser
+antialiasing can still vary between renders. Do not use whole-image PNG or decoded-RGBA
+byte equality as proof of frame selection: check the rendered media content and its
+reported time and geometry. A pinned profile does not certify pixel parity with Discord.
+
 The report includes viewer, channel, target and modal IDs, published and render generations, geometry,
 media metadata (effective frame times, codec selection, transformations), readiness, calibration,
 action status and diagnostics. Captures reject unsettled actions, unavailable authorization,

{simcord-3.2.0 → simcord-3.2.1}/docs/guides/time-control.md

@@ -73,6 +73,34 @@ latest-Env fallback, global datetime patch, or general application-time virtuali
 Inject `env.now` into your application's own clock seam. Only one live Env per event
 loop is supported; a second start rejects before altering hooks.
 
+Executor ownership follows actual execution, not the caller's Future. Native
+cancellation that removes a queued job prevents execution; cancelling a shielded
+or non-forwarding facade does not. Cancelling a running job never claims that its
+thread stopped. Work it enqueues before completion retains bot ownership.
+
+While Envs are active, paired, reference-counted hooks observe owned submissions
+through the standard `ThreadPoolExecutor.submit` and `ProcessPoolExecutor.submit`
+APIs, including interpreter pools where available. Unrelated submissions retain
+their original behavior; SimCord neither replaces nor shuts down supplied
+executors. Native rejection, initializer failure and completion retire the
+actual job independently of the facade. Isolated process/interpreter pools
+receive only the original picklable callable, not an Env or its in-process state.
+The hooks are restored when the last Env detaches.
+
+SimCord preserves the original executor hook and caller Future. Custom hooks
+should forward the submitted callable unchanged to the native executor. An
+opaque callable adapter can hide pre-entry cancellation or rejection, leaving
+ownership unresolved and timing out rather than guessing that no work remains.
+A custom hook can also hide later asynchronous post-processing behind an
+already-completed facade; settlement cannot join that invisible work. The hook
+must expose or await its own completion. Captured callback context is preserved
+when later work is scheduled.
+
+A shutdown timeout while draining native work retains the gateway, shards and
+webhook adapter until a later successful drain. The attempt may already have
+cancelled asynchronous tasks: it is not a rollback. Release outstanding work
+and retry shutdown.
+
 !!! tip "Stepwise vs. one jump"
     `advance_time` consumes timers in order, settling between each, so intermediate effects
     actually happen. If a handler sleeps 30s, posts, then sleeps another 30s and posts

simcord-3.2.1/jsconfig.preview.json

@@ -0,0 +1,17 @@
+{
+  "compilerOptions": {
+    "allowJs": true,
+    "checkJs": true,
+    "noEmit": true,
+    "noResolve": true,
+    "strict": true,
+    "target": "ES2022",
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "lib": ["ES2022", "DOM", "DOM.Iterable"]
+  },
+  "include": [
+    "src/simcord/preview/static/*.js",
+    "src/simcord/preview/static/*.d.ts"
+  ]
+}

simcord-3.2.1/package-lock.json

@@ -0,0 +1,27 @@
+{
+  "name": "simcord-preview-checks",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "simcord-preview-checks",
+      "devDependencies": {
+        "typescript": "5.9.3"
+      }
+    },
+    "node_modules/typescript": {
+      "version": "5.9.3",
+      "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz",
+      "integrity": "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "bin": {
+        "tsc": "bin/tsc",
+        "tsserver": "bin/tsserver"
+      },
+      "engines": {
+        "node": ">=14.17"
+      }
+    }
+  }
+}

simcord-3.2.1/package.json

@@ -0,0 +1,11 @@
+{
+  "name": "simcord-preview-checks",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "check:preview": "tsc --project jsconfig.preview.json"
+  },
+  "devDependencies": {
+    "typescript": "5.9.3"
+  }
+}

{simcord-3.2.0 → simcord-3.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "simcord"
-version = "3.2.0"
+version = "3.2.1"
 description = "Offline discord.py bot testing with pytest. No network, token, or test server."
 readme = "README.md"
 license = "MIT"