docs(31): capture phase context
This commit is contained in:
@@ -0,0 +1,174 @@
|
||||
# Phase 31: Chat polish against WavePath clients - Context
|
||||
|
||||
**Gathered:** 2026-11-13
|
||||
**Status:** Ready for planning
|
||||
|
||||
<domain>
|
||||
## Phase Boundary
|
||||
|
||||
WavePath's community traffic is recorded from the PHP backend with `tide`, replayed against Go, and Go is fixed until the replay is green. "Community traffic" is wider than the roadmap entry's wording (D-09): every route under `/_wave/api/v1/community`, the guest routes, the push routes and the bot and token routes, about 190 routes, plus every realtime publication those routes cause.
|
||||
|
||||
The replay target is a new application repo, `sm-wavepath-app`, which mounts the seven shared chat plugins and serves the recorded `/_wave` paths from an in-repo `wavepath` app plugin. That plugin ports only what the recorded routes exercise. It is the start of WavePath's Go app, not the whole app port.
|
||||
|
||||
Out of scope:
|
||||
- The rest of WavePath's backend (diary, practices, trainings, stats, auth, journal, payments, admin screens). They come with the later WavePath phases.
|
||||
- The MariaDB to Postgres import, the production cutover and the pre-freeze re-record (D-06).
|
||||
- `electron-wavepath` and `tauri-wavepath-desktop` as separate recording clients. The roadmap names three clients: `vue-wavepath-app`, `wavepath-mcp` and `hubot-wavepath`.
|
||||
- Any commit in the `wavepath.org` repo (D-08).
|
||||
|
||||
**Repos touched:**
|
||||
- `sm-wavepath-app` (new): app skeleton, `wavepath` app plugin, `parity/` corpus, seeders, recording scripts, the gate script.
|
||||
- The seven shared plugin repos, for parity fixes and re-freeze deltas: `sm-chat-plugin`, `sm-chatchannels-plugin`, `sm-chatbots-plugin`, `sm-chatvideo-plugin`, `sm-forum-plugin`, `sm-herald-plugin`, `sm-userfriends-plugin`.
|
||||
- `sm-user-plugin`, only additively and only if a recorded route needs it.
|
||||
- `summercms.go`, only for `tide` or `lighthouse` gaps.
|
||||
- `sm-demo-app`, `sm-bm-app` and the vue layers (`vue-chat-layer`, `vue-chatvideo-layer`, `vue-forum-layer`, `vue-userfriends-layer`), to follow shared-plugin changes (D-15) and for the folded todos.
|
||||
- `sm-oauthserver-plugin`, for the folded OIDC parity recording.
|
||||
|
||||
**Roadmap corrections** (make them in the first planning commit):
|
||||
- "Depends on": remove Phase 30. Keep Phase 19 and Phase 19.1 (D-05).
|
||||
- "Repos": replace with the list above.
|
||||
- Success criterion 1: the corpus is the community surface defined in D-09, not only "chat, channel, thread, video-room and push routes".
|
||||
- Success criterion 2: every publication of every writing step, on any namespace (D-10).
|
||||
- Success criterion 3: name the gate from D-15. `sm-bm-app` and `sm-demo-app` build and pass their tests with the released plugin versions.
|
||||
|
||||
</domain>
|
||||
|
||||
<decisions>
|
||||
## Implementation Decisions
|
||||
|
||||
### Replay target and paths
|
||||
- **D-01:** **Recorded `/_wave` requests replay unchanged against `/_wave` routes served by Go.** A Go app mounts the seven plugins and an in-repo `wavepath` app plugin registers the recorded paths as aliases over the plugin services. `tide` gets no path-rewrite feature, and the plugin test hosts get no `/_wave` aliases. This is the "thin aliases" route that P19 D-07 and P19.1 D-05 left open for the WavePath port.
|
||||
- **D-02:** **The app is a new sibling repo, `sm-wavepath-app`,** laid out like `fonoteka.go`: `summer.yaml`, shared plugins as git submodules at `plugins/golem15/<name>`, the app plugin in-repo, `parity/` with the manifest, fixtures, capture rules and broadcast goldens, a `replace` of the framework to `../summercms.go` during development. WavePath's own agent later grows the same repo for the rest of the app port. — **Reversibility:** costly — the repo name, module path and `parity/` layout are what WavePath's agent and every later WavePath phase build on.
|
||||
- **D-03:** **The app plugin ports whatever the recorded routes need, not only aliases.** That includes the controller logic of WavePath's community controllers and the host seams: the channel and forum access resolvers, the bot auth resolver, the herald profile and presence gate, the notification dispatch, the group context adapter and the group lifecycle wiring (a created group spawns its chat and channels, a deleted group ends video and removes the forum context). Routes outside the corpus stay unported.
|
||||
- **D-04:** **One named scenario, seeded on both sides.** The scenario (users in each role, groups, channels, conversations, an existing thread, pins, a call link, forum content, friendships, a bot, a guest) is defined once. A PHP reset script seeds it into the local WavePath database, and a Go fixture plugin in `sm-wavepath-app` seeds the same rows into Postgres, as `fonoteka.go/parity` does with `fonoteka_reset.php` and `fixtureplugin`. `summer import:winter` is not used here.
|
||||
|
||||
### Recording source and timing
|
||||
- **D-05:** **Phase 31 does not depend on Phase 30.** The user: "phase 30 was meant for plytarium cutover, wavepath is totally separate project". The roadmap dependency was sequencing only.
|
||||
- **D-06:** **Record now, re-record before the WavePath freeze.** The corpus is recorded from today's PHP and Go is fixed against it. Shortly before the WavePath cutover the whole corpus is re-recorded with a drift report and each drift is resolved (the Phase 30 D-12 pattern). That re-record belongs to the WavePath cutover phase. Phase 31 must leave it runnable unattended.
|
||||
- **D-07:** **Proxy once, then scripted specs.** The three real clients run through `summer parity:proxy` once to learn the exact requests, headers and bodies they send. Those sessions become committed spec flows that `summer parity:record` re-runs without a person.
|
||||
- **D-08:** **The PHP backend is the local checkout at `/media/nvme/dev/jz/wavepath.org`,** brought up by a script this phase delivers: the PHP server, its database with the D-04 scenario, Centrifugo pointed at the `tide` recorder, and LiveKit and the push service answered by the `tide` upstream proxy. Nothing is committed in `wavepath.org`. The reset script and the env overlay live in `sm-wavepath-app/parity` and are applied from outside. The phase may check the PHP submodules out at the commits the repo pins and may write to the local dev database.
|
||||
|
||||
### Corpus boundary
|
||||
- **D-09:** **The corpus is WavePath's community surface, about 190 routes:**
|
||||
- everything under `/_wave/api/v1/community`: `groups` (108 routes, group administration included), `dm`, `threads`, `prefs`, `forums`, `friends`, `notes`, `status`, `join`, `presence`, `call-links`, `call-guest`;
|
||||
- `/_wave/api/v1/guest/*` (call-link knock, guest session, guest thread and reactions);
|
||||
- `/_wave/api/v1/push/*`;
|
||||
- the bot and token routes under `/api/v1` (`conversations`, `conversations/{id}/messages`, `realtime/token`) and the `/hooks/{token}` webhook.
|
||||
|
||||
The researcher re-counts from `routes.php` at the recording commit and lists any route under these prefixes that no client calls.
|
||||
- **D-10:** **Every publication of every writing step is asserted.** Each corpus step that writes gets a broadcast golden with all publications PHP sent for it, on any namespace (`chat`, `video`, `presence:`, `user`, `wave`). Channel authorization (the Centrifugo subscribe proxy and `realtime/token`) is replayed as ordinary routes.
|
||||
- **D-11:** **Case depth is client paths plus denials.** Per route:
|
||||
- the cases the clients produced in the proxy sessions;
|
||||
- one denial per access rule (unauthenticated 401, non-member 403 or 404);
|
||||
- the validation errors the UI can trigger (422);
|
||||
- one 429 case per named rate bucket.
|
||||
|
||||
Outbound LiveKit and web-push calls are recorded as `tide` upstream sidecars and asserted on replay.
|
||||
|
||||
### Drift and fix policy
|
||||
- **D-12:** **The port contract is re-frozen at the recording commit.** It replaces the commits in P19 D-01 and P19.1 D-01. The WavePath commit and its pinned submodule commits are written into the manifest. Every delta since the old freeze that the corpus exercises is ported in this phase: into the shared Go plugin when the PHP change is in a shared plugin (chat `943b712..fbfbcf9`, attachment streaming with Range support), into the app plugin when it is in `wavepath` (guest threads and guest identity). — **Reversibility:** costly — names and shapes from the new freeze are copied into every app that mounts the shared plugins.
|
||||
- **D-13:** **Go reproduces PHP's observable behaviour, quirks included.** The one exception is a security defect (data reaching a non-member, a missing access check): Go keeps the safe behaviour, and the case goes into an accepted-differences file with its reason. The user signs off each entry. Precedent: the Phase 19.5 email-proof divergence.
|
||||
- **D-14:** **The PHP shape wins in the shared plugins; consumers follow.** A parity fix corrects the shared serializer or behaviour itself, so the generic `/_x/api/v1` APIs and the `/_wave` aliases keep one serializer set. Each changed plugin gets a patch tag and a changelog post on `/changelog/plugins`, and `sm-demo-app` and the vue layers are updated in this phase. A renamed or removed field is called out in the release notes. The user's condition: "1 is fine as long as sm-bm-app keeps working". Before any plugin tag, `sm-bm-app` (mounts chat, chatchannels and chatbots, with its own frontend) must build with the new plugin commits, pass its tests (`chat_test.go`, `realtime_test.go`), and have its frontend checked against any renamed or removed field. — **Reversibility:** costly — a changed field in a published plugin API reaches every mounting app and vue layer.
|
||||
- **D-15:** **The phase closes at zero pending.** Every corpus route is `ported` with passing cases, every broadcast golden is asserted, and the only non-matching cases are signed entries in the accepted-differences file. A fail-closed gate script checks this, and checks that `sm-bm-app` and `sm-demo-app` build and pass. The gate lives in `sm-wavepath-app`, because a script in `summercms.go` would name an application.
|
||||
|
||||
### Claude's Discretion
|
||||
- Go package, type and route-handler names in the app plugin, and the layout inside `parity/`.
|
||||
- The scenario's exact rows, as long as every access rule in D-11 has a user on each side of it.
|
||||
- How the PHP reset script is run against the checkout without committing there (artisan tinker, a script path, a mounted file).
|
||||
- The name of the gate script and of the accepted-differences file.
|
||||
- Whether `tide` needs additions (for example more broadcast normalisation rules for chat payloads). Any such change is generic, documented in `modules/tide/README.md` and names no application.
|
||||
- The module path and git remote of `sm-wavepath-app`. Creating a remote and pushing need the user's go-ahead.
|
||||
- Plan count and split, subject to the plan-count checkpoint and "unit tests are the last plan". This is a large phase; say so at the checkpoint and propose a split into decimal phases if the count gets unwieldy.
|
||||
- Run the security-review agent: the app plugin adds guest access, bot and token authentication, a webhook and access resolvers.
|
||||
|
||||
### Folded Todos
|
||||
- **Record PHP OIDC parity against WavePath before the OIDC cutover** (`2026-10-19-record-php-oidc-parity-against-wavepath.md`, `sm-oauthserver-plugin`). Phase 19.4 shipped the harness but never recorded PHP. The local WavePath stack from D-08 is exactly what the todo's runbook needs, so the recording is done here: follow `../sm-oauthserver-plugin/testdata/parity/README.md` until `PHASE194_REQUIRE_PARITY=1 go test -run '^(TestPHPParityReplay|TestIDTokenShapeParity)$' ./...` passes. It is separate from the community corpus and lives in the plugin repo.
|
||||
- **Chat messages that start with "/" but name no command are posted as text** (`chat-slash-text-escape.md`, `../vue-chat-layer/app/composables/useChat.ts`). Every text starting with "/" is dispatched as a command and refused. Fix in the layer: dispatch only when the first token is a known trigger from the command catalog, or support a "//" escape. The researcher first checks what `vue-wavepath-app` and the PHP command controller do with such text and matches that.
|
||||
- **Moderate profile names, friend-group names and chat attachment filenames** (`moderation-profile-group-and-filenames.md`, `../sm-demo-app/plugins/demo/moderation.go`). The demo's filter covers only message content and forum text. Add the checks through additive seams (a user-plugin saving event, a group saving seam in userfriends, filenames on chat's message-saving event). The seams are additive and must leave PHP parity untouched: with no listener, behaviour is unchanged.
|
||||
|
||||
</decisions>
|
||||
|
||||
<canonical_refs>
|
||||
## Canonical References
|
||||
|
||||
**Downstream agents MUST read these before planning or implementing.**
|
||||
|
||||
### The contract (PHP, read-only)
|
||||
- `/media/nvme/dev/jz/wavepath.org/plugins/golem15/wavepath/routes.php` — the route table. Groups at lines 195 (auth), 222 (guest), 252 (JWT API, community routes inside), 948 and 1022 (`/api/v1` token and bot), 1073 (`/hooks`).
|
||||
- `/media/nvme/dev/jz/wavepath.org/plugins/golem15/wavepath/controllers/api/` — the community controllers whose logic D-03 ports (`CommunityForumController`, `CommunityFriendsController`, `CommunityGroupController`, `CommunityVideoController`, `CommunityCommandController`, `CommunitySharedNoteController`, `BotRestController`, `PushSubscriptionController`).
|
||||
- `/media/nvme/dev/jz/wavepath.org/plugins/golem15/wavepath/Plugin.php` — seam bindings and group lifecycle wiring (lines 160-460 at the old freeze; re-check at the recording commit).
|
||||
- `/media/nvme/dev/jz/wavepath.org/plugins/golem15/wavepath/classes/{chatbots,notifications,forum,video}/` — the host implementations of the seams.
|
||||
- `/media/nvme/dev/jz/wavepath.org/plugins/golem15/{chat,chatchannels,chatbots,chatvideo,forum,herald,userfriends}` — the shared plugins. The repo pins chat at `fbfbcf9`; the working tree had it at `943b712` on 2026-11-13.
|
||||
- `/media/nvme/dev/jz/wavepath.org/vue-wavepath-app/src/`, `/media/nvme/dev/jz/wavepath.org/wavepath-mcp/src/`, `/media/nvme/dev/jz/wavepath.org/hubot-wavepath/src/` — the three clients that are recorded.
|
||||
- `/media/nvme/dev/jz/wavepath.org/.planning/notes/summercms-framework-asks-for-wavepath.md` — WavePath's hand-off list; section B is what its own agent ports later.
|
||||
|
||||
### Prior decisions that still bind
|
||||
- `.planning/phases/19-chat-and-chatchannels/19-CONTEXT.md` — D-02 (no QuestStream trace), D-06 to D-10 (generic API, one serializer set), D-11 to D-14 (context registry, alias rewrite, festival hooks, deny-all resolvers), D-16 and D-17 (lighthouse namespaces). D-01's commits are superseded by D-12 here.
|
||||
- `.planning/phases/19.1-chat-satellites/19.1-CONTEXT.md` — D-05 (satellite generic APIs and rate buckets), D-08 (group lifecycle is app wiring), D-10 (push through fetchguard), D-13 to D-15 (LiveKit, reconciler, video events).
|
||||
- `.planning/phases/30-cutover/30-CONTEXT.md` — D-11 and D-12, the manifest acceptance set and the re-record with a drift report that D-06 and D-15 copy.
|
||||
- `.planning/notes/2026-10-18-roadmap-reorder-demo-release-wavepath.md` and `.planning/notes/wavepath-framework-asks-division.md` — why this phase opens the WavePath work.
|
||||
- `.planning/seeds/SEED-261007-0tb-wavepath-port.md` — size of the whole WavePath port.
|
||||
- `.planning/notes/core-plugins-own-repos.md` — plugin commit, tag and submodule pointer workflow.
|
||||
|
||||
### Tooling and patterns to copy
|
||||
- `modules/tide/README.md` — flows, recording proxy, capture rules, manifests, the Centrifugo recorder and broadcast goldens, upstream sidecars and the upstream recording proxy.
|
||||
- `../fonoteka.go/parity/` — the model for D-02 and D-04: `manifest.yaml`, `fixtures/`, `capture-rules.yaml`, `capture_clients.mjs`, `fonoteka_reset.php`, `fixtureplugin/`, `broadcast_goldens_test.go`, `upstream/`.
|
||||
- `../fonoteka.go/scripts/dev-stack.sh` — the fail-closed local stack script, a model for D-08.
|
||||
- `../sm-demo-app/summer.yaml`, `../sm-demo-app/chat_test.go`, `../sm-demo-app/realtime_test.go` — an app that already mounts all seven plugins.
|
||||
- `../sm-bm-app/summer.yaml`, `../sm-bm-app/chat_test.go`, `../sm-bm-app/realtime_test.go` — the consumer D-14 protects.
|
||||
|
||||
### Folded todos
|
||||
- `.planning/todos/pending/2026-10-19-record-php-oidc-parity-against-wavepath.md` and `../sm-oauthserver-plugin/testdata/parity/README.md`
|
||||
- `.planning/todos/pending/chat-slash-text-escape.md`
|
||||
- `.planning/todos/pending/moderation-profile-group-and-filenames.md`
|
||||
|
||||
</canonical_refs>
|
||||
|
||||
<code_context>
|
||||
## Existing Code Insights
|
||||
|
||||
### Reusable Assets
|
||||
- `tide`: everything the recording needs exists (loopback proxy with sessions, spec recording, manifest record and replay, Centrifugo recorder, broadcast goldens, upstream sidecars). It has no request-path rewriting, which D-01 makes unnecessary. Its broadcast normalisation has rules written for album and notification payloads; chat payloads may need generic additions.
|
||||
- The seven shared plugins, each with a typed service API, a generic `/_x/api/v1` API, a test-only host and `testdata/goldens/` built from PHP fixtures (never from a live PHP backend).
|
||||
- `sm-demo-app`: mounts all seven plugins and has chat, realtime and video tests; a working reference for wiring contexts and resolvers.
|
||||
- `lighthouse`: namespaces `chat`, `video` and `user` are registered by the plugins. `presence:` and `wave` belong to the app plugin.
|
||||
|
||||
### Established Patterns
|
||||
- App parity suite in the app repo, `go test ./parity` on testcontainers Postgres, pending never counts as a pass.
|
||||
- One scenario seeded by a PHP reset script and a Go fixture plugin.
|
||||
- Fail-closed per-phase gate script.
|
||||
- Plugin first (commit, push, tag), then the submodule pointer bump in each app as a separate commit.
|
||||
|
||||
### Integration Points
|
||||
- `sm-wavepath-app` registers the group context alias, installs the access resolvers, bot auth, herald profile and presence gate, and wires group lifecycle events to chat, channels, video and forum.
|
||||
- Consumers of the shared plugins today: `sm-demo-app` (all seven) and `sm-bm-app` (chat, chatchannels, chatbots).
|
||||
- The local PHP checkout has uncommitted work and belongs to another agent; the recording script must not leave changes in its working tree beyond the submodule checkouts and the dev database.
|
||||
|
||||
</code_context>
|
||||
|
||||
<specifics>
|
||||
## Specific Ideas
|
||||
|
||||
- "phase 30 was meant for plytarium cutover, wavepath is totally separate project": no ordering against the Płytarium work.
|
||||
- "local wavepath is there in /media/nvme/dev/jz/wavepath.org we can work with it": use that checkout for the recording.
|
||||
- "1 is fine as long as sm-bm-app keeps working": `sm-bm-app` is a hard gate on every shared-plugin release.
|
||||
|
||||
</specifics>
|
||||
|
||||
<deferred>
|
||||
## Deferred Ideas
|
||||
|
||||
- The pre-freeze re-record with a drift report: a task of the WavePath cutover phase (D-06).
|
||||
- The rest of WavePath's backend and the MariaDB to Postgres import: later WavePath phases, owned with WavePath's agent.
|
||||
- `electron-wavepath` and `tauri-wavepath-desktop` as recording clients: with the full-surface corpus at the cutover.
|
||||
- A manual session of the real clients against the Go app: not required to close this phase (D-15); belongs to the cutover.
|
||||
|
||||
### Reviewed Todos (not folded)
|
||||
- The other ten matches were keyword noise and concern other work: the WinterCMS vs SummerCMS benchmark, gate scripts that name applications, changelog previous/next links, the forum and friends 401 refresh, MailBlocker, the menu plugin port, the first password for social accounts, README `src=` fences, the fonoteka README and the translate messages editor.
|
||||
|
||||
</deferred>
|
||||
|
||||
---
|
||||
|
||||
*Phase: 31-chat-polish-against-wavepath-clients*
|
||||
*Context gathered: 2026-11-13*
|
||||
@@ -0,0 +1,193 @@
|
||||
# Phase 31: Chat polish against WavePath clients - Discussion Log
|
||||
|
||||
> **Audit trail only.** Do not use as input to planning, research, or execution agents.
|
||||
> Decisions are captured in CONTEXT.md — this log preserves the alternatives considered.
|
||||
|
||||
**Date:** 2026-11-13
|
||||
**Phase:** 31-chat-polish-against-wavepath-clients
|
||||
**Areas discussed:** Replay target and paths, Recording source and timing, Corpus boundary, Drift and fix policy
|
||||
|
||||
---
|
||||
|
||||
## Todo cross-reference
|
||||
|
||||
13 pending todos matched; ten were keyword noise. Three were offered.
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| None | Fold nothing | |
|
||||
| PHP OIDC parity | Record PHP OIDC parity against WavePath (sm-oauthserver-plugin) | ✓ |
|
||||
| Slash text escape | "/" text that names no command is refused (vue-chat-layer) | ✓ |
|
||||
| Moderate filenames | Moderate profile names, group names and attachment filenames (sm-demo-app) | ✓ |
|
||||
|
||||
**User's choice:** all three folded.
|
||||
|
||||
---
|
||||
|
||||
## Replay target and paths
|
||||
|
||||
### How recorded /_wave traffic reaches the Go plugins
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| /_wave aliases in a Go app | App skeleton mounts the plugins and serves the recorded paths, host seams wired | ✓ |
|
||||
| Path map in tide | Generic rewrite rules in tide, replay against the generic API on a test host | |
|
||||
| Aliases in plugin test hosts | Each plugin's test host registers /_wave-shaped aliases | |
|
||||
|
||||
### Where the app skeleton and corpus live
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| New sm-wavepath-app | Sibling repo laid out like fonoteka.go | ✓ |
|
||||
| Inside the wavepath.org repo | Go directory next to the PHP code | |
|
||||
| Throwaway parity host | Parity-only module, aliases rewritten later | |
|
||||
|
||||
### Diffs caused by Wave controller logic
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Port what chat routes need | App plugin ports controller logic and host seams for the recorded routes | ✓ |
|
||||
| Thin aliases only | Controller-caused diffs stay pending for the app port | |
|
||||
| You decide per route | Researcher classifies, planner picks | |
|
||||
|
||||
### Starting state
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| One scenario, seeded twice | PHP reset script plus Go fixture plugin | ✓ |
|
||||
| Import the PHP database | summer import:winter into Postgres | |
|
||||
| Flows build their own state | No shared seed beyond users | |
|
||||
|
||||
**User's choice:** the recommended option each time.
|
||||
|
||||
---
|
||||
|
||||
## Recording source and timing
|
||||
|
||||
### When the corpus is recorded
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Now, re-record before cutover | Record from today's PHP, re-record with a drift report before the freeze | ✓ |
|
||||
| Build now, record later | Binding corpus waits until the migration is near | |
|
||||
| Wait for Phase 30 | Keep the roadmap order | |
|
||||
|
||||
**User's choice:** free text first: "Why would it depend on phase 30, phase 30 was meant for plytarium cutover, wavepath is totally separate project". After the clarification that the dependency was sequencing only, the user chose option 1.
|
||||
**Notes:** the Phase 30 dependency is removed from the roadmap entry.
|
||||
|
||||
### How traffic is captured
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Proxy once, then scripted specs | Learn the real requests through the proxy, commit spec flows | ✓ |
|
||||
| Real clients through the proxy only | Every recording is a live session | |
|
||||
| Scripted specs from source | Specs written from the clients' API code | |
|
||||
|
||||
### Which PHP backend
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Local stack, scripted | Phase delivers a script that brings up the local checkout | ✓ (as interpreted) |
|
||||
| Local stack, you start it | User starts the stack | |
|
||||
| Staging through a tunnel | Deployed staging over SSH | |
|
||||
|
||||
**User's choice:** free text: "local wavepath is there in /media/nvme/dev/jz/wavepath.org we can work with it".
|
||||
**Notes:** recorded as the local checkout, brought up by a script from this phase.
|
||||
|
||||
### What may be written in wavepath.org
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Nothing committed there | Reset script and env overlay live in sm-wavepath-app/parity | ✓ |
|
||||
| A parity/ directory in wavepath.org | Committed on a branch there | |
|
||||
| Hand it to WavePath's agent | Spec only, implemented by the other agent | |
|
||||
|
||||
---
|
||||
|
||||
## Corpus boundary
|
||||
|
||||
### Neighbouring route groups (multi-select)
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Forum and friends | community/forums (16), community/friends (8) | ✓ |
|
||||
| Bot and token REST | /api/v1 conversations, realtime/token, /hooks/{token} | ✓ |
|
||||
| Guest calls and guest thread | /_wave/api/v1/guest/* and community/call-guest | ✓ |
|
||||
| Shared notes and status | community/notes, status, join | ✓ |
|
||||
|
||||
### How much of community/groups
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| All of community/* | About 190 routes with guest, push and bot/token | ✓ |
|
||||
| Chat-facing group routes only | Group administration left to the app port | |
|
||||
| All, split in two phases | Chat core in 31, the rest in 31.1 | |
|
||||
|
||||
### Realtime assertions
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Every publication of every write step | All namespaces, authorization routes replayed | ✓ |
|
||||
| Only chat, video and presence: | user and wave publications pending | |
|
||||
| Goldens for a chosen event list | Only events the clients listen to | |
|
||||
|
||||
### Case depth
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Client paths plus denials | Client cases, one denial per rule, UI validation errors, upstream sidecars | ✓ |
|
||||
| Client paths only | Only what the proxy sessions produced | |
|
||||
| Full matrix | Every role and every rule | |
|
||||
|
||||
---
|
||||
|
||||
## Drift and fix policy
|
||||
|
||||
### Port contract after PHP drift
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Re-freeze at the recording commit | Deltas the corpus exercises are ported in this phase | ✓ |
|
||||
| Keep the old freeze, park the drift | Drift diffs pending | |
|
||||
| Record from the old commits | PHP submodules checked out at the frozen commits | |
|
||||
|
||||
### PHP quirks and bugs
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Reproduce, except security | Signed accepted-differences file for security defects | ✓ |
|
||||
| Reproduce everything | Unsafe behaviour fixed on PHP first | |
|
||||
| Fix obvious bugs in Go | Each listed as an accepted difference | |
|
||||
|
||||
### Releasing shared-plugin fixes
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| PHP shape wins, layers follow | Patch tags, changelog posts, demo app and vue layers updated | ✓ |
|
||||
| Additive only in shared plugins | /_wave alias adapts output in the app plugin | |
|
||||
| Ask per breaking change | Stop on removed, renamed or retyped fields | |
|
||||
|
||||
**User's choice:** free text: "1 is fine as long as sm-bm-app keeps working".
|
||||
**Notes:** sm-bm-app mounts chat, chatchannels and chatbots; it is a hard gate before every plugin tag.
|
||||
|
||||
### Closing bar
|
||||
|
||||
| Option | Description | Selected |
|
||||
|--------|-------------|----------|
|
||||
| Zero pending, signed exceptions | Fail-closed gate, sm-bm-app and sm-demo-app pass | ✓ |
|
||||
| Chat core green, rest may pend | Named pending list for the next phase | |
|
||||
| Green plus a manual client session | Adds a manual session of the three clients | |
|
||||
|
||||
---
|
||||
|
||||
## Claude's Discretion
|
||||
|
||||
- Names and layout in the app plugin and `parity/`, the scenario's rows, how the PHP reset script runs from outside the checkout, gate and accepted-differences file names, generic `tide` additions, the module path and remote of `sm-wavepath-app`, plan count and split.
|
||||
- The gate script lives in `sm-wavepath-app` rather than `summercms.go/scripts`, so that no framework script names an application.
|
||||
|
||||
## Deferred Ideas
|
||||
|
||||
- Pre-freeze re-record with a drift report (WavePath cutover phase).
|
||||
- The rest of WavePath's backend and the database import.
|
||||
- electron and tauri clients as recording clients.
|
||||
- A manual session of the real clients against the Go app.
|
||||
Reference in New Issue
Block a user