diff --git a/.eslintrc.cjs b/.eslintrc.cjs index d2a138cf..9d5a27d9 100644 --- a/.eslintrc.cjs +++ b/.eslintrc.cjs @@ -1,8 +1,3 @@ -// Airbnb's own bans, kept: a `no-restricted-syntax` entry below replaces the whole list. -const airbnbRestrictedSyntax = require('eslint-config-airbnb-base/rules/style').rules[ - 'no-restricted-syntax' -]; - module.exports = { env: { browser: true, @@ -67,21 +62,6 @@ module.exports = { "@typescript-eslint/no-shadow": "error" }, overrides: [ - { - // The one join path: a join is `joinEstateRoom`, which files the DM before it sends the join. - files: ['src/**/*.ts', 'src/**/*.tsx'], - excludedFiles: ['src/app/features/estate/joinEstateRoom.ts', 'src/**/*.test.*'], - rules: { - 'no-restricted-syntax': [ - ...airbnbRestrictedSyntax, - { - selector: "CallExpression[callee.property.name='joinRoom']", - message: - 'Join a room through joinEstateRoom (features/estate/joinEstateRoom.ts), the one join path.', - }, - ], - }, - }, { files: ['*.ts'], rules: { diff --git a/.github/workflows/build-pull-request.yml b/.github/workflows/build-pull-request.yml index 964add54..11b5056c 100644 --- a/.github/workflows/build-pull-request.yml +++ b/.github/workflows/build-pull-request.yml @@ -4,14 +4,12 @@ on: pull_request: types: ['opened', 'synchronize'] -concurrency: - group: ${{ github.workflow }}-pr-${{ github.event.pull_request.number }} - cancel-in-progress: true - jobs: build-pull-request: name: Build pull request runs-on: ubuntu-latest + env: + PR_NUMBER: ${{github.event.number}} steps: - name: Checkout repository uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 @@ -26,3 +24,17 @@ jobs: env: NODE_OPTIONS: '--max_old_space_size=4096' run: npm run build + - name: Upload artifact + uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1 + with: + name: preview + path: dist + retention-days: 1 + - name: Save pr number + run: echo ${PR_NUMBER} > ./pr.txt + - name: Upload pr number + uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1 + with: + name: pr + path: ./pr.txt + retention-days: 1 diff --git a/.github/workflows/docker-pr.yml b/.github/workflows/docker-pr.yml index 24b9389c..997aba6d 100644 --- a/.github/workflows/docker-pr.yml +++ b/.github/workflows/docker-pr.yml @@ -6,10 +6,6 @@ on: - 'Dockerfile' - '.github/workflows/docker-pr.yml' -concurrency: - group: ${{ github.workflow }}-pr-${{ github.event.pull_request.number }} - cancel-in-progress: true - jobs: docker-build: runs-on: ubuntu-latest diff --git a/.github/workflows/lockfile.yml b/.github/workflows/lockfile.yml index e96d2818..a9cc1a34 100644 --- a/.github/workflows/lockfile.yml +++ b/.github/workflows/lockfile.yml @@ -5,10 +5,6 @@ on: paths: - 'package-lock.json' -concurrency: - group: ${{ github.workflow }}-pr-${{ github.event.pull_request.number }} - cancel-in-progress: true - jobs: lockfile_changes: runs-on: ubuntu-latest diff --git a/.github/workflows/rat-dev-preview.yml b/.github/workflows/rat-dev-preview.yml index 47f22b7e..45da8bc4 100644 --- a/.github/workflows/rat-dev-preview.yml +++ b/.github/workflows/rat-dev-preview.yml @@ -4,13 +4,6 @@ on: push: branches: ['dev'] -# One run per ref wins: a newer push to dev cancels the older queued or running one, so the run -# that builds rat-dev-dist is always the newest. Pull-request runs are other workflows and other -# groups; they never cancel it. -concurrency: - group: rat-dev-preview - cancel-in-progress: true - jobs: build: name: Build dev preview diff --git a/README.md b/README.md index abeba8b2..dfc722ad 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ and your own place in it) instead of an invite list. Mobile first. **Live now:** the Cinny engine (matrix-js-sdk, Rust crypto, sync) under a Ratatoskr UI: branding, GameCult theme, estate navigation, pose portraits -(opt-in setting), a background scene (on in the dev config, `backgroundScene.tier`; the device can lower it) and an opt-in soundscape. +(opt-in setting), a background scene and soundscape (opt-in, off by default). **Planned:** see [`docs/gamecult/ratatoskr-target.md`](docs/gamecult/ratatoskr-target.md) for the target and cut sequence. Internal names that are protocol or stored state (`cinny_*` localStorage keys, the `in.cinny.room.power_level_tags` event diff --git a/config.json b/config.json index fea9a59e..dd4c887b 100644 --- a/config.json +++ b/config.json @@ -1,40 +1,24 @@ { - "defaultHomeserver": 0, - "homeserverList": [ - "chat.gamecult.org" - ], - "allowCustomHomeservers": false, + "defaultHomeserver": 1, + "homeserverList": ["converser.eu", "matrix.org", "mozilla.org", "unredacted.org", "xmr.se"], + "allowCustomHomeservers": true, "featuredCommunities": { "openAsDefault": false, - "spaces": [ - "#gamecult:gamecult.org" + "spaces": ["#gamecult:gamecult.org"], + "rooms": [ + "#tuwunel:grin.hu", + "#free-software-movement:matrix.org", + "#gentoo:matrix.org" ], - "rooms": [], - "servers": [ - "gamecult.org" - ] + "servers": ["activematrixrooms.com", "matrixrooms.info", "matrix.org", "mozilla.org", "unredacted.org"] }, + "hashRouter": { - "enabled": true, + "enabled": false, "basename": "/" }, + "backgroundScene": { - "tier": "full", - "style": "ridge" - }, - "dings": { - "enabled": false - }, - "fileZoneShare": { - "enabled": false - }, - "push": { - "vapidPublicKey": "", - "gatewayUrl": "", - "appId": "" - }, - "registration": { - "enabled": false, - "url": "" + "tier": "off" } } diff --git a/docs/file-zone-mind-contract.md b/docs/file-zone-mind-contract.md deleted file mode 100644 index 8b350c6c..00000000 --- a/docs/file-zone-mind-contract.md +++ /dev/null @@ -1,98 +0,0 @@ -# File zone: what a Mind can read from a file event - -Ruling `ratatoskr:ruling:persona-file-sharing-zone`. The Mind-side fetch is the mouth's -(`eureka-body:cut_spec:mouth-fetch-attachment.r1`); this page is the client side of the same contract. -A Mind cannot fetch an `mxc://` itself (the media endpoint answers 401), so it never holds one. - -## What the Mind passes - -Room id and event id of the file event. Never a bare `mxc://`, URL or hash. The mouth fetches the event, -reads the media reference from its content, and enforces the Mind's own membership in that room at fetch -time. A room the Mind is not in is refused by the mouth, whatever the client wrote. - -## What the client writes (this repo, `RoomInput.tsx` send path) - -A file event is an `m.room.message` whose `msgtype` is `m.audio`, `m.image`, `m.video` or `m.file`: - -| field | where | note | -| ------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `msgtype` | content | selects the kind from the file's mimetype prefix | -| `body`, `filename` | content | both the file's name (display only; never a path) | -| `url` | content | the `mxc://` of an unencrypted file; the mouth reads it | -| `file` | content | present instead of `url` in an encrypted room: `{url, key, iv, hashes.sha256 (ciphertext), v}`. A Mind has no key; the mouth refuses it | -| `info.mimetype` | content | the browser-reported type, normalised by `safeFile` (e.g. `application/ogg` becomes `audio/ogg`). A claim, not proof: the mouth sniffs magic bytes | -| `info.size` | content | bytes of the file as uploaded | -| `info.sha256` | content | lower-case hex sha256 of the plaintext bytes, computed by the client before send; written in unencrypted rooms only (a plaintext hash in an encrypted room would leak the file's identity) | - -The hash is computed over the same bytes that are uploaded, reading the whole file into memory before send (large videos pay for it); if hashing fails the file is sent without one. A file sent by something other than this -client may lack `info.sha256`; the mouth then logs the hash it computed, and the row can show no `fetched for` -for it. - -`info.mimetype` and `info.size` are written on audio and file events always; on image and video events `info` exists only if the browser could load the media, otherwise `info` holds `sha256` alone. Image and video events also carry `info.w`, `info.h`, `info.xyz.amorgan.blurhash` and a thumbnail -reference; audio carries no duration. A Mind should not rely on any of those. - -## Limits and refusals - -- Size: the mouth streams at most 5 MiB and refuses a larger file. The client does not enforce this cap; - its own limit is the homeserver's `m.upload.size`. A file over 5 MiB can be shared with people and - not fetched for a Mind. -- Refusals are the mouth's and are typed: not a member of the room, bridged or Discord room, encrypted - file, over the cap, content type not matching the magic bytes. The client does not re-check them and - nothing in the client depends on the mouth's log. -- The Mind cites files by room id and event id only; a file in a room the Mind is not in does not exist - for it. - -## Receipt: `org.gamecult.file_received` - -The Mind posts one event of type `org.gamecult.file_received` after a successful fetch, to the room of the -file. When the file has an album root the receipt is a reply in the album's thread, so it arrives with the album's -own listing; otherwise (a composer file sent with no thread) it is a plain room event with no `m.relates_to`. Both -count, and the client finds a receipt by its `event_id` anywhere in the room's loaded timeline or the album's thread: - -```json -{ - "m.relates_to": { "rel_type": "m.thread", "event_id": "" }, - "org.gamecult.file_received": { - "event_id": "", - "sha256": "", - "size": 123456 - } -} -``` - -A plain room-event receipt may also carry `m.relates_to: {rel_type: "m.reference", event_id: }`, which lets -the mouth find its earlier receipts through `/relations` for dedup. The client matches by `content.event_id` and reads no -relation but this one: if a `m.reference` is present its `event_id` must equal `content.event_id`, else the receipt counts -for nothing. A thread relation is not read. However many receipts a Mind has posted for a file, the row draws one -`fetched for` for that Mind. - -Two rules, both enforced on each side: - -1. **The sender is the Mind.** The row trusts the Matrix `sender` of the receipt event and nothing inside it: - no Mind field is read. `fetched for X` counts only when the sender is X's own Matrix identity (the - full id is `@:` for a Mind in the Persona catalogue; a display name, a lookalike or another server's `@void:evil.example` does not count). -2. **Fetched means verified.** The Mind posts only after the sha256 of the bytes it fetched equals the file - event's `info.sha256`, and the receipt carries that hash. On a mismatch it posts nothing (or a typed - refusal that the row does not draw). The row checks it again: the receipt's `sha256` must equal the - file event's `info.sha256`. A file event with no `info.sha256` can show no `fetched for`. - -The receipt is inert: no paths, URLs, filenames or anything a browser would fetch, and the client reads only -`event_id`, `sha256` and the sender. It has no `msgtype`, so the album's file listing ignores it. The mouth's -log is the fuller record for Minds; this event is the public tick. - -The row draws `fetched for `: one receipt per Mind per file (the latest), several Minds side by side. A -receipt for an event that is not a file of that album, a malformed one, and a redacted one are ignored. -The wording is deliberate: the receipt says the mouth fetched and stored the file for the Mind, not that it is in the Mind's sandbox and not that it was read. Client strings never say "saved" or "read". -The sender check keeps a member from ticking for a Mind; it does not prove the Mind read the file beyond -what the hash and the Mind's own account show. - -## Not built yet - -- Files sent from the composer carry no thread relation, so they reach an album only if written into a - thread by another tool; the album upload path (docs/file-zone.md, "Upload") is unwritten. Their receipts are plain - room events, and the timeline row for the file shows `fetched for` from them. -- A receipt that is still encrypted when it arrives is not seen until a later timeline event triggers a rescan; zones are - unencrypted and the hash is written only there, so this is the encrypted-room limit again. -- The timeline row reads the room's loaded timeline only: a receipt older than what the client has paged in is not - seen there (an album's own listing reads the thread, which is paged separately). -- Encrypted zones are not listed. diff --git a/docs/file-zone.md b/docs/file-zone.md deleted file mode 100644 index 7990485d..00000000 --- a/docs/file-zone.md +++ /dev/null @@ -1,123 +0,0 @@ -# File zone: design sketch - -Status: design only. No code exists. Everything below is a proposal; items marked **UNKNOWN** are not yet verified against the Body. - -Source: Meta ruling 2026-10-31, eureka mind `ratatoskr:ruling:file-zone-looks-like-file-sharing`. - -## What it is - -A file-sharing space beside the room timeline, not a view of it. The zone is **one ordinary Matrix room with threaded discussions, one thread per Mind**. The UI presents each thread as an **album** (title, item count, date) and each post in it as a **file** with an inline player or preview. Matrix is the storage and the fallback: another client sees a normal room with threads and never needs the zone. No homeserver change. - -First use (Aqua): listen to audio in place, mark each clip keep / fix / drop with a one-line reason, export the marks as a file. See `/opt/commons/handoff/aqua-listen-kits-20261108/` (static `listen.html` kits that emit `verdict.json` + `verdict.md`); the zone replaces sending that page around. - -## Matrix event shapes (stock events only) - -- **Zone** = one room, chosen by the client (**UNKNOWN:** how the client knows which room is the zone: a room-account-data flag, a `m.room.create` type, or a configured room id in `config.json`; config is simplest). -- **Album** = a thread root: a text `m.room.message` posted by a Mind, `body` = the album title (the Mind's name, e.g. `void`). One thread per Mind, owned by authorship (the root's sender). **UNKNOWN:** whether a Mind may open more than one (e.g. per kit); the shape allows it with no change, the zone would then list several albums per author. Count and last-activity come from the SDK's thread summary (`unsigned.m.relations.m.thread`); album date = root `origin_server_ts`. Rename = `m.replace` on the root. -- **File** = a post in the thread: an `m.room.message` with `msgtype` `m.audio` / `m.image` / `m.video` / `m.file` and `m.relates_to: { rel_type: "m.thread", event_id: , is_falling_back: true, "m.in_reply_to": { event_id: } }`. The builders in `src/app/features/room/msgContent.ts` already make the content. Delete = redact. -- **Album vs chat thread**: with a single-purpose room, every thread is an album. No marker key is needed. A non-media reply in a thread (chat, a mark) is not a file and is not listed as one. -- **Cover** = first image file in the thread, if any. Loose room messages outside any thread are not shown in the zone; they remain in the timeline. - -## Marks (reactions, plus an optional reply) - -A mark is stock Matrix, so every client shows it. Two reaction sets on the **file post**, and one optional reply: - -- **Verdict** = an `m.annotation` reaction (`m.reaction` event, `m.relates_to: { rel_type: "m.annotation", event_id: , key }`) with key **👍 keep**, **🔧 fix**, **🗑 drop**. One per person per file: choosing another replaces the old one (the client redacts the sender's previous verdict reaction, then sends the new one); tapping the active one clears it. -- **Landed** = a second reaction set, keys **1️⃣ 2️⃣ 3️⃣ 4️⃣ 5️⃣** (keycap digits, 1-5). Also one per person per file, same replace rule. The two sets are independent: a file can have a verdict, a landed score, both or neither. -- **Reason** = an ordinary thread reply under the file: `m.room.message` `m.text`, `m.relates_to: { rel_type: "m.thread", event_id: , "m.in_reply_to": { event_id: } }`. Optional. **Keep needs none**; the UI prompts for one mainly after fix or drop. The latest such reply by the sender under that file is the reason (edits via `m.replace` count). No special key: the reply text is the reason, so nothing is lost if another client wrote it. -- **No private mode.** Marks are room events the moment they are tapped; there is no local-only draft and no "Share" step. Offline taps queue in the SDK's normal send queue. -- Who marked what is read from the reactions' senders, so each listener is distinguishable and the album can show tallies per file. -- Why reactions: one tap, readable in any client, no custom event type, and they can be changed with no history growth beyond a redaction. Reaction keys carry no text, hence the separate reply for the reason. -- **UNKNOWN:** emoji variation selectors. 🗑 and 🔧 and the keycaps may arrive with or without U+FE0F from different clients; match by normalizing (strip U+FE0F) before comparing keys. Also **UNKNOWN:** servers' per-event limits on distinct reaction keys; a handful per file is far below any default. - -## Export - -Client-side only. "Export" builds Aqua's verdict file from the verdict and landed reactions and the reply under each file in one album (one listener's marks per export; that sender is the `listener`) and either downloads it or uploads it into the album. Two files, as the kits write them: `verdict.json` and `verdict.md`. - -`verdict.json` is schema **`aqua.listen.verdict.v1`**, field for field what `buildVerdict` in the kit (`dings/listen.html`, section `buildVerdict`) emits, so Aqua's tooling reads it unchanged: - -``` -{ schema: "aqua.listen.verdict.v1", - kit: { id, title }, // album root: id = root event id (or the kit id if the upload carried one), title = root body - exportedAt, // ISO time of export - seed, consent, // kit-only: zone writes seed: 0 (or omits), consent: true for the sender's own export (see UNKNOWN) - listener, // sender display name - device, // headphones|speakers|null, the sender's most-used mark device, or null - notes, // free text; zone leaves "" in v1 - summary: { total, keep, fix, drop, unanswered }, - clips: [{ position, id, title, group, feel, file, pair, slot, verdict, reason, landed, device }], - pairs: [{ a, b, preferred }] } // empty array when the album has no pairs -``` - -- `clips` has one row per file post in the album, in thread order (`position` = 1-based). The join per file, for the exporting listener: `verdict` = their 👍/🔧/🗑 reaction (keep/fix/drop) or null; `landed` = their keycap reaction (1-5) or null; `reason` = text of their latest reply under the file, or "". A file with no verdict reaction counts as `unanswered` even if it has a reply. `device` per clip is null (reactions cannot carry it); the top-level `device` (headphones|speakers|null) is asked once in the export dialog. -- `pairs`, `seed`, `consent` are optional for the zone: `pairs: []`, no `slot`/`pair` (null) unless the clip metadata supplies them. -- **Where clip metadata comes from.** `id` is the clip id from `org.gamecult.clip`, else the filename stem. `title` = file post `body`; `file` = the post's `filename`/`body`. `group`, `feel`, `pair`, `slot` are kit data that Matrix has no slot for: carry them on the file post as one extra key `org.gamecult.clip: { id, group, feel, pair, slot }` written by whoever uploads the kit (a small uploader script, **UNKNOWN**, not in the first slice; without it those columns export as ""/null and the id falls back to the filename stem). -- `verdict.md` follows `verdictMarkdown` from the same file: header line, count line, the clip table (`# | clip | group | intended feel | verdict | landed (1-5) | device | reason`), pairs table when `pairs` is nonempty, notes. -- To avoid drift, the exporter should be a port of `buildVerdict`/`verdictMarkdown` with the schema string and field order pinned by a test that compares against a fixture produced by the kit. **UNKNOWN:** whether to share code (the kit's `logic.cjs`) rather than port; recommend port, ~80 lines, because the kit is a standalone page. -- **UNKNOWN:** `consent` is a kit-side checkbox before listening. The zone has no such step; recommend writing `true` only if the sender ticks a one-time "include my name in exports" toggle, else `false` and `listener: ""`. -- JSON here is a xenos-boundary export, not state; the room events are the state. - -## Mobile-first layout - -- Phone width is the design width; desktop adds columns. -- Level 1, album list: one column, each row = cover/icon, title, "N files", date. Tap opens. -- Level 2, album: list by default (title, duration/size), grid toggle for images. Audio rows play in place, one at a time (starting a clip stops the last), a persistent mini-player at the bottom with seek. -- Mark controls on each audio row: three large tap targets (👍 keep / 🔧 fix / 🗑 drop) with tallies, a row of five "landed" chips (1-5), and after fix or drop an inline one-line reason field (skippable). Thumb-reachable, no modal. -- Back is one level up; the room timeline stays one tap away (the zone is a sibling view, not a replacement). **UNKNOWN:** where the entry lives in the room header; check `RoomViewHeader.tsx`, `Room.tsx` for how the member drawer and pin menu attach. - -## Upload - -Reuse the composer's pipeline, pointed at an album instead of the main timeline: - -- `createUploadAtom` / `useBindUploadAtom` (`src/app/state/upload.ts`), `UploadCard`, `upload-board` for progress. -- On success, the msgContent builder produces the event; the zone adds the thread relation to the album root before sending (the composer already does this for thread replies, `RoomInput.tsx`). -- "New album" = send the root text event, then upload into its thread. Multi-file drop = N events, sent in order. -- Size limit from `MediaConfigLoader` (server `m.upload.size`). **UNKNOWN:** whether the 32 MB `shelf` kit's clips (42 x ~0.75 MB) should be uploaded individually or batched; individually is the only option without a server change. - -## Existing code to reuse (verified present in the repo) - -| need | where | -| --------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| audio player (play/seek/volume, encrypted download) | `src/app/components/message/content/AudioContent.tsx` (210 lines) | -| video, image, generic file | `.../content/VideoContent.tsx`, `ImageContent.tsx`, `FileContent.tsx` | -| full-screen image viewer | `src/app/components/image-viewer/ImageViewer.tsx` | -| media dispatch by msgtype | `src/app/components/RenderMessageContent.tsx`, `message/MsgTypeRenderers.tsx` | -| upload + progress | `state/upload.ts`, `components/upload-card`, `upload-board` | -| event content builders | `features/room/msgContent.ts` | -| thread plumbing | `features/room/message/Message.tsx`, `RoomTimeline.tsx`, `RoomInput.tsx` (thread relation on send) | -| room-scoped file/pin precedent | `features/room/room-pin-menu/RoomPinMenu.tsx` | - -Nothing named "gallery" exists as a feature; `AudioContent` takes its controls as render props (`renderMediaControl`), so it can be rehosted in a row without a fork. **UNKNOWN:** whether `AudioContent` can be rendered outside a timeline event context (it needs only `url`, `info`, `mimeType`, `encInfo`, from the event content, so probably yes). - -## First slice (what to build first) - -Rough lines of TypeScript, tests excluded. - -1. **Read-only albums + album view** (~250 lines): list the room's thread roots as albums (grouped or filterable by author = Mind), open one to list its file posts, rehost `AudioContent` and `ImageContent`. One route/panel plus a header entry. Depends on the thread list the SDK already keeps. -2. **Marks + export** (~240 lines, with the schema port): verdict and landed reaction sets with the replace-one rule, optional reason reply, per-file tallies, the join into `aqua.listen.verdict.v1` and `verdict.json`/`verdict.md` download. This is Aqua's workflow end to end. -3. **Upload into an album** (~150 lines): thread-related send through the existing upload atoms, "new album". - -Slices 1+2 serve the first use case. Each is its own PR. Because marks are ordinary thread replies, there is no separate "publish" slice. - -## Open questions for the Meta - -- How the client identifies the zone room (config id recommended). -- Whether exports are per listener (proposed) or a merged all-listeners file. -- Where `device` comes from, now that reactions cannot carry it (export dialog, proposed). - -## Share a set (built, behind `fileZoneShare.enabled`) - -The ruling `ratatoskr:ruling:persona-file-sharing-zone` asks that a set of files arrive together, not one attachment at a time. The zone already holds one thread per album, so a set is an album: **one root text message plus one `m.thread` reply per file**, the exact shape `buildAlbums` reads. Nothing new on the wire and no homeserver change; a Mind's mouth that posts into the zone room and a person using the client produce the same events. - -Matrix options checked: (a) a thread, chosen: stock, rendered by every client, already the zone's album; (b) `m.gallery` (MSC4274) puts several items in one event, but it is unstable, most clients and this one do not render it, and each item still needs its own upload; (c) a shared custom relation: no client groups by it. A thread costs one extra event per set (the root) and nothing else. - -Client, `src/app/features/albums`: - -- `shareSet.ts`: `sendShareSet(port, title, files)`. Sends the root, then each file in pick order, each reply falling back to the previous event (`threadRelation`). A file whose upload fails is named in the result and the rest still go; a root that fails to send throws before any upload. The root alone is not an album in the list (`/threads` returns only roots that have a reply), so a share where every upload failed leaves a lone text message in the timeline. After a send the panel keeps only the failed files picked; a retry makes a second album. Ports are injected, so the order and failure rules are tested without a homeserver (`shareSet.test.ts` reads the sent events back through `buildAlbums`). -- `shareController.ts`: the panel's state machine (picked files, phase, the one-send-per-room guard, the encrypted refusal, failed files kept by position), apart from React so tests drive it without a DOM; `shareController.test.ts` and `ShareSet.test.tsx` (static render of each state, the flag) pin it. No DOM test environment exists in this repo, so a real tap on a real input is covered by the phone check, not by tests. -- `ShareSet.tsx`: phone layout. Idle, it is one text row, "Share files". Picking files (any number from the native picker; a second pick replaces the first) mounts a title field, the picked names on one dim line, and Send / Cancel as full-width rows; progress is "Sending 2 of 5". It is shown only on the album list (kept mounted but hidden while an album is open, so a running send keeps its state), one send at a time per room (tracked outside the component; leaving the page does not stop a send, it only loses its progress and result), and never in an encrypted zone (re-checked when Send is tapped) (the plaintext `info.sha256` the Mind verifies against is written in unencrypted rooms only). -- Content per file comes from `getMsgContent` in `features/room/msgContent.ts`, now also used by the composer, so a shared file and an attached file carry the same `info` including `sha256`. - -Flag: `fileZoneShare.enabled` in `config.json`, default `false`. With it off nothing mounts. - -Not built: a Mind's own path into the zone (outbox, Persona decision, mouth post) belongs to gamecult-ops / Huginn / the mouth, not this client; sharing into an existing album ("add files"); upload cancel; pagination beyond 100 albums/files. diff --git a/docs/gamecult/chat-shell-compression.md b/docs/gamecult/chat-shell-compression.md deleted file mode 100644 index c8ac66cd..00000000 --- a/docs/gamecult/chat-shell-compression.md +++ /dev/null @@ -1,108 +0,0 @@ -# chat.gamecult.org: shell compression and caching - -Follow-up `ratatoskr:follow_up:chat-shell-compression`. Measured 2026-11-12 against the live -host, which serves release `ratatoskr-nemesis-9b9b495d` (the `index-CAataSJe.js` bundle; the offline table -below also uses the `f8115609` handoff build, `index-D0yL0Dgy.js`, and says which row is which). The host config is -`nginx/chat.gamecult.org.conf` in `gamecult-ops`, owned by Eureka; nothing here is applied -to the host. - -## What the host serves now - -The 2026-10-31 probe (no Content-Encoding, no Cache-Control on `/assets/`) is stale: the -`nginx.conf` has `gzip on`, the site file sets level 5, `gzip_vary` and `gzip_types` for js, css, json, svg and wasm, and carries an immutable -`Cache-Control` on `/assets/` and `/preview/assets/`. Probed with `curl -H 'Accept-Encoding: X'`. - -| Resource | raw | gzip (served now) | brotli (served now) | -|---|---|---|---| -| `/assets/index-CAataSJe.js` | 3,732,771 | 956,085 | none: `br` is ignored, identity returned | -| `/assets/index-BLdKqKqx.css` | 111,267 | 19,952 | none | -| `/assets/matrix_sdk_crypto_wasm_bg-DwIieW7K.wasm` | 5,573,870 | 1,878,147 | none | -| `/` (index.html, no-cache) | 3,066 | gzip | none | - -Headers: hashed `/assets/` answer `Cache-Control: public, max-age=31536000, immutable`; -`/`, `index.html`, `sw.js`, `manifest.json`, `config.json` answer `no-cache`; compressed -responses carry `Vary: Accept-Encoding` and a weak ETag. `config.json` (424 B) is below -`gzip_min_length 1024` and goes uncompressed, which is correct. - -So the original ask is done. What is left is brotli, which nginx 1.26.3 here cannot serve: -`/usr/sbin/nginx -V` shows `--with-http_gzip_static_module` and no brotli module. - -## What brotli buys - -Level-5 gzip is what the host does per request. Offline measurement on the same files -(node `zlib`, 2026-11-12): - -| File | raw | gzip 5 (node) | gzip 9 | brotli 11 | brotli vs live | -|---|---|---|---|---|---| -| live main chunk `index-CAataSJe.js` | 3,732,771 | 957,199 | 945,424 | 725,167 | -24% | -| handoff main chunk `index-D0yL0Dgy.js` | 3,868,313 | 1,015,680 | 1,001,446 | 773,992 | -24% | -| crypto wasm | 5,573,870 | 1,868,282 | 1,851,108 | 1,343,595 | -28% | -| `ReactPrism-Dm2uRF4v.js` | 577,517 | 209,339 | 208,376 | 163,525 | -22% | - -A cold load of the two big files falls from about 2.8 MB to about 2.1 MB on the wire; the -saving is ~0.7 MB once per hashed build per device while the HTTP cache keeps the file (immutable; the -service worker does no precaching, so eviction or a new device pays again). gzip 9 alone buys 1-2%, so -`gzip_static` without brotli is not worth a build step. Brotli is the whole prize, and it -needs one root step. - -Cost: brotli q11 takes about 12 s for the wasm and 8 s for the main chunk on one core, so -the whole dist is about two minutes at build time (measured, 84 files) and zero CPU per request. Do not use q11 -on the fly; that is why the plan is precompressed twins. - -## Root list for Eureka (host) - -1. `apt install libnginx-mod-http-brotli-filter libnginx-mod-http-brotli-static` (trixie/main, 1.0.0~rc-6, - depend on `nginx-abi-1.26.3-1`, which the installed nginx provides; apt may offer an nginx patch upgrade - alongside, say so before accepting). Do not enable the config yet. -2. Install a build with twins (`PRECOMPRESS=1`, below) the usual way - (`docs/gamecult/client-build-install.md`). Twins for files that are not there change nothing. -3. In the `chat.gamecult.org` `server` block, beside the existing gzip lines: - -```nginx - brotli_static on; # serve .br when the client sends br - gzip_static on; # serve .gz; falls back to the on-the-fly gzip above - brotli on; # on-the-fly br for files with no twin (index.html, small files) - brotli_comp_level 5; - brotli_types text/css application/javascript text/javascript application/json application/manifest+json image/svg+xml application/wasm; -``` - - The `location ^~ /assets/` block and `/preview/`, `/element/` and `/mockups/` inherit these; they only add headers. - No other change: the `Cache-Control` and `Vary` lines stay as they are, and - `gzip_vary on` already makes the on-the-fly and static paths vary correctly. -4. `nginx -t && systemctl reload nginx`. Twins first, config second: with `brotli on` and no twins every - client gets on-the-fly q5 brotli of the 3.7 and 5.6 MB files, which costs CPU per request. - -Rollback: remove the five lines and reload. The `.br`/`.gz` files can stay on disk, unused. - -## Build side - -`build-prod-dist.sh` (Void's, in `/opt/commons/handoff/ratatoskr-main-build/`) gains -`PRECOMPRESS=1`, which runs `precompress.cjs ` before the manifest is written. It -writes `.br` (q11) and `.gz` (level 9, no mtime, deterministic for one node) next -to each js, css, wasm, json, svg, html file over 1 KiB, only when smaller than the original. -Default is off, so builds installed before the host change do not ship ~27 MB of twins that -nothing serves. The twins appear in `SHA256SUMS`; the determinism compare still applies. -Tested on `ReactPrism-Dm2uRF4v.js` (gzip roundtrip identical to the original); a full -`PRECOMPRESS=1` build has not been run because it waits on step 1. - -The script is not in this repo; its placement is a standing open item of the build handoff. - -## Before/after measurement - -Run from any machine; `X` is the asset URL. Before = today's table above. - -```sh -for ae in identity gzip br; do - printf '%s ' "$ae"; curl -s -o /dev/null -H "Accept-Encoding: $ae" -w '%{size_download} %header{content-encoding}\n' "$X" -done -curl -sI -H 'Accept-Encoding: br' "$X" | grep -iE 'content-encoding|vary|etag|cache-control' -``` - -Pass: with `br` the main chunk is about 774 KB and the wasm about 1.34 MB with -`Content-Encoding: br`; with `gzip` the bytes are no larger than today; with `identity` -the file is the raw size; `Vary: Accept-Encoding` and the immutable `Cache-Control` are -still present on all three; `index.html`, `sw.js` and `config.json` still `no-cache`. -The service worker's registration and an existing session must still work (open chat on -the operator's phone, hard reload once, check the network panel's "transferred" column). -Check `/preview/assets/` the same way, but `/preview/` is served from `/srv/cinny/preview`, which this build -script does not produce: it gets on-the-fly brotli, not twins, until a preview build carries them. diff --git a/docs/gamecult/client-build-install.md b/docs/gamecult/client-build-install.md deleted file mode 100644 index b2505fe1..00000000 --- a/docs/gamecult/client-build-install.md +++ /dev/null @@ -1,121 +0,0 @@ -# Ratatoskr client: build, install, verify, roll back - -Who does what. The steward (Void) builds and hands off; Void holds no root and does not deploy. -Eureka installs on the chat.gamecult.org host, which is Eureka's. This page is the shared -procedure. Nothing here is run by the build step against the live host. - -## Facts about the host - -- Web root: `/srv/cinny/`. `current` is a symlink to one directory under `releases/`; the web - server serves `current`. Releases are `releases/ratatoskr-<8hex>` (older ones are - `ratatoskr-nemesis-<8hex>`). Previous releases stay on disk; that is the rollback. -- The client is static. `config.json` sits in the release root beside `index.html` and is read - at load. Cinny's `Dockerfile` and `docker-nginx.conf` are upstream's container path, not the - chat.gamecult.org path. -- Check the pointer before anything else: `readlink /srv/cinny/current`. - -## 1. Build (steward) - -Two builds exist, and they treat `config.json` differently. - -**By hand (the repo's config).** `vite build` copies the repo's `config.json` into `dist/` -(`vite.config.js`, static copy of `config.json`). Ratatoskr #103 made the repo file the intended -served config, and #106 set `backgroundScene.style` to `ridge`; the served file has not caught up -(see Open). Do not hand-edit `dist/config.json`. - -```sh -git clone https://eureka.gamecult.org/forge/GameCult/Ratatoskr.git && cd Ratatoskr -git checkout # build a named commit, not a branch tip -npm ci --ignore-scripts # .npmrc sets legacy-peer-deps; skips husky's prepare hook -node scripts/sync-poses.mjs # pose art is not committed; this also rewrites the tracked - # src/app/components/message/pose/catalogue.json -NODE_OPTIONS=--max_old_space_size=6144 npm run build # writes dist/ -``` - -Skip `sync-poses` and the build ships with no poses. Do not use `npm run build:preview` for -production: it rewrites `dist/config.json` for preview (hash router, chosen tier and style). - -**The handoff build (what the host installs).** -`/opt/commons/handoff/ratatoskr-main-build/build-prod-dist.sh ` (see its `README.md`) -writes `/opt/commons/handoff/ratatoskr-main-/{dist,SHA256SUMS,BUILD-INFO,build.log}`, -locks the files read-only and refuses to overwrite. The dist carries the repo's `config.json` at -that sha (BUILD-INFO `config_json_source`, `config_json_sha256`); there is no separate pinned copy. -Its live check always runs: it fetches the served config and compares it byte for byte with the -repo's. A difference prints the diff and stops the build. `ALLOW_CONFIG_DRIFT=1` builds anyway and -BUILD-INFO records `config_json_live_check: DIFFERS ...` and `config_json_live_sha256`, so the -handoff states which config differs and the installer decides. From Yggdrasil the public name does -not resolve: pass `LIVE_CURL_ARGS="--resolve chat.gamecult.org:443:127.0.0.1"`. -The folder, with the three pins (`SHA256SUMS` sha256, `BUILD-INFO` sha256, lockfile sha256) and -the node and npm versions, is what the install request names. -Every build stamps its commit into `index.html` (`scripts/buildSha.js`): ``, -with `-dirty` appended when the tree had uncommitted changes and `unknown` when there was no git. Where git governs the tree it decides: an explicit `BUILD_SHA` naming a different commit than HEAD stamps `-mismatch`, a git failure stamps `unknown`. A full-sha `BUILD_SHA` stands only for a tree git does not govern (a source archive) or cannot read (unusable git, for example a dubious-ownership refusal). The handoff -build refuses a dist whose stamp differs from the sha it was asked for, and prints the stamp in its block. -To read it from anywhere: `curl -s https://chat.gamecult.org/ | grep -o 'build-sha" content="[^"]*'`. - -Before handing off: - -```sh -cd /dist && sha256sum -c ../SHA256SUMS # 0 failures -grep -rl 'demo.invalid\|demo-preview-token' /dist # must print nothing -# from Yggdrasil the public name may not resolve; --resolve points it at the local server -diff <(curl -fsS --resolve chat.gamecult.org:443:127.0.0.1 https://chat.gamecult.org/config.json) /dist/config.json -``` - -A config difference is a finding to report, not something to paper over: either live drifted or -the repo is wrong, and a ruling (Meta, for `backgroundScene.style`) says which ships. - -## 2. Install (host owner, root, by hand) - -Note the rollback target first: `readlink /srv/cinny/current`. - -Unpack beside the live release; do not touch the live directory. The target must not exist, or -`cp -r` nests `dist` inside it. - -```sh -R=ratatoskr-<8hex> -H=/opt/commons/handoff/ratatoskr-main- -test ! -e /srv/cinny/releases/$R -cp -r $H/dist /srv/cinny/releases/$R -cmp /srv/cinny/current/config.json /srv/cinny/releases/$R/config.json -(cd /srv/cinny/releases/$R && sha256sum -c $H/SHA256SUMS) -``` - -`cmp` is a drift check, not a pass check. Live has no trailing newline; the repo's file has one, -so even equal content differs. Read the difference (`diff` the two) and settle which config -ships. To keep the host's config byte-for-byte, as past installs did, -`cp /srv/cinny/current/config.json /srv/cinny/releases/$R/config.json`; `sha256sum -c` then flags -`config.json` only (read that one line; `--ignore-missing` does not hide a mismatch). - -Switch (a single symlink swap; `ln -sfn` unlinks then links, so there is a moment with no link): - -```sh -ln -sfn releases/$R /srv/cinny/current -``` - -## 3. Verify - -- `readlink /srv/cinny/current` names `releases/$R`. -- `curl -s https://chat.gamecult.org/config.json | sha256sum` equals `sha256sum /srv/cinny/releases/$R/config.json`. -- Load https://chat.gamecult.org/ and hard-refresh (the service worker, `sw.js`, can hold the - previous assets). Sign-in card shows, the background scene draws, the browser console has no - page errors, a poses/asset request returns 200 and not index.html. - -## 4. Roll back - -Point `current` at the release noted before the switch. Live at the time of writing is -`ratatoskr-nemesis-9b9b495d`: - -```sh -ln -sfn releases/ratatoskr-nemesis-9b9b495d /srv/cinny/current -``` - -Hard-refresh to clear `sw.js`. Do not delete the failed release; leave it for diagnosis. - -## Open - -- The served config (checked 2026-11-12) is not the repo's: it says `backgroundScene.style` - `terrain` where the repo says `ridge` (#106, Meta 2026-11-11), lacks the repo's `dings`, - `fileZoneShare` and `registration` blocks (all off in the repo), and has no trailing newline. - The new keys default off or inert when absent, so only the style is a decision. Meta says which - style ships. Until the served file is replaced, every handoff build stops at the live check - unless `ALLOW_CONFIG_DRIFT=1` is set (section 1). diff --git a/docs/gamecult/ratatoskr-target.md b/docs/gamecult/ratatoskr-target.md index b56c90f8..166c5c72 100644 --- a/docs/gamecult/ratatoskr-target.md +++ b/docs/gamecult/ratatoskr-target.md @@ -1,7 +1,7 @@ # Ratatoskr: target and prose map Ratatoskr is GameCult's Matrix chat client: this fork of Cinny, forge -`GameCult/Ratatoskr` (renamed from `GameCult/cinny`; the forge redirects the old name). +`GameCult/cinny` (to be renamed `GameCult/Ratatoskr`; see the cut sequence). Void stewards it. Campaign `ratatoskr` lives in the eureka mind for now, beside the rulings it rests on. Under `eureka-body:ruling:ruling-home-steward-mind` it is handed to Void's mind once, by procedure, as soon as that hand-off procedure @@ -346,6 +346,7 @@ Each later cut is one line, with what it waits on. attention document, scoped to room members; waits on Huginn publishing it. - `rename-ratatoskr`: package name, app name and branding, manifest and titles, the `/preview/` path and its deploy, and every in-repo `cinny` - reference that is ours (not upstream engine paths). The forge rename of - `GameCult/cinny` to `GameCult/Ratatoskr` is done - (`eureka-body:ruling:chat-client-named-ratatoskr`). + reference that is ours (not upstream engine paths); waits on Void's forge + rename of `GameCult/cinny` to `GameCult/Ratatoskr` + (`eureka-body:ruling:chat-client-named-ratatoskr`), and the campaign's repo + list moves with it. diff --git a/docs/mind-feedback-pages.md b/docs/mind-feedback-pages.md deleted file mode 100644 index 9ff45d08..00000000 --- a/docs/mind-feedback-pages.md +++ /dev/null @@ -1,242 +0,0 @@ -# Mind feedback pages - -> The desk reads `gamecult.fork.*` now, not the `org.gamecult.feedback.*` projections named below; see CultLib `contracts/cultnet/governance/fork-card.md` (src/app/features/desk/forkContract.ts). - -Design only. No code exists for this; nothing here is built. Drafted by Kiko Self (2026-11-07) with Heimdall's draft rulings -on guests and hiding; placement ruled for this repo by Void. Follow-up `eureka-body:follow_up:ratatoskr-mind-feedback-pages`. -Every number below is provisional. - -**Schema owner.** The Huginn kinds, their fields, keys and refusals are specified in `huginn-feedback-kinds-proposal.md` (Eureka Self, 2026-11-07, in -`/opt/commons/handoff`), adopted for this page by Void's Persona. Where this page names a field of those kinds it mirrors that proposal; if they differ, the proposal wins. -This repo owns only the client: a typed interface mirroring those shapes, and fixtures. - -Each Mind's section in the estate navigator opens on that Mind's **feedback page**: the Mind's open questions with options, its -recommendation and what each waits on, answerable by the operator and anyone with an account. It replaces the old Fork Desk -(taken from the brief; no trace of it was found in this repo or in the Minds' state). - -## 1. Placement - -Each Mind's navigator section **opens on its feedback page**, rooms below it. A cross-Mind list of everything waiting on a person -is wanted later and is not part of this spec. On phones the page folds each question's options and the answer form behind its title, -so the section root stays a list of questions, not a wall of forms. - -## 2. Authority - -| Concern | Owner | The page's part | -|---|---|---| -| The question | a typed `question` document in the **owning Mind's own mind**, key `:question: