You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c6cec64
Browse filesBrowse the repository at this point in the historyBrowse files
docs: make native development the acceptance path (#666)
Signed-off-by: Carl <32a2e2c9d428ee08902cab75d956da2c1d235a22d4766b0dd4138bf6e2e5db1d@buzz.block.builderlab.xyz>
Co-authored-by: Carl <32a2e2c9d428ee08902cab75d956da2c1d235a22d4766b0dd4138bf6e2e5db1d@buzz.block.builderlab.xyz>
authorization and publication outcomes are separate layers. Existing host-specific
267
+
checks remain necessary until the corresponding broker endpoint is retired; retain
268
+
the Rust regression cases when removing the Node consumer.
269
+
270
+
**Manual testing of anything that ships uses `BUZZ_DEV_VIEWER= just desktop`.**
271
+
The explicit empty value overrides a pin inherited from `.env.local`; merely
272
+
unsetting the shell variable does not. This selects the shipped native code path,
273
+
not the release credential namespace or a release bundle. Packaging, OS integration
274
+
and release-specific behavior still need the appropriate packaged-build checks.
275
+
Broker-backed runs, including pinned native windows, do not count as acceptance.
276
+
They remain useful for browser diagnostics and existing broker tests, but do not
277
+
prove native signing, OS storage, networking or filesystem behavior.
278
+
279
+
Report the exact snapshot and host/mode exercised. Native/live acceptance needs an
280
+
agreed isolated identity/data setup; browser fixtures and test identities must
281
+
never use real keys. Do not launch a native app or switch someone's active identity
282
+
merely to follow this testing guidance.
283
+
284
+
### Broker reduction sequence
285
+
286
+
The following is the proposed removal order, not authorization to delete current
287
+
browser workflows. Each slice must identify its callers, move needed regression
288
+
coverage to the shipped owner, and delete displaced code in the same change. A
289
+
whole broker endpoint/module can go only after its browser use is explicitly
290
+
retired or replaced; do not weaken a still-callable endpoint to reduce duplication.
291
+
292
+
| Order | Existing `dev/` responsibility | Reduction and exit condition |
293
+
| --- | --- | --- |
294
+
| 1 |`user-status.mjs`| Remove repeated text/emoji policy in favor of the existing `src/features/relay` owner. Keep remaining broker shape/time enforcement only while its status endpoint is supported; do not copy it into Rust incidentally. |
295
+
| 2 |`channel-kit.mjs`, `session-commands.mjs`, `direct-messages.mjs`, signing branches in `relay-broker.mjs`| Retire browser write capabilities one feature at a time after native acceptance and replacement fixture coverage. Remove each Node validator/encryption helper with its last caller; keep native signing tests. |
296
+
| 3 |`read-state.mjs`, `sidebar-{preferences,mutes,sort,stars}.mjs`| Retire encrypted-state broker routes and their Node copies once browser callers no longer need them. Shared frontend edit policy and native custody remain. |
297
+
| 4 |`agent-memory.mjs`, `agent-observer.mjs`, `archive.mjs`, `project-git.mjs`, `attachment-{file,upload}.mjs`, `media-preparation.mjs`| Remove feature-by-feature after archive/observer, repository and media browser uses are retired or replaced and native failure/recovery coverage is retained. Do not delete user data or migrate credentials as cleanup. |
298
+
| 5 |`relay-broker.mjs` and its declaration | Remove residual routes and the custom stream bridge only after their consumers and broker-backed fixtures are retired or replaced. Any shared-transport replacement is a separate design decision, not an assumed prerequisite. |
299
+
300
+
Developer tools (`developer-settings.ts`, `live-setup-probe.mjs`) are not Rust
301
+
feature mirrors. Legacy library and hosted-community helpers (`agent-library.mjs`,
302
+
`builderlab.mjs`) need separate caller/capability decisions before removal; they
303
+
are not automatically replaced by native identity. This sequence adds no new
304
+
backend and changes no runtime defaults or credentials.
262
305
263
306
## Interactive product iteration
264
307
265
308
While shaping the first version, default to **edit → human tries the running app
266
309
→ adjust**. A manual feedback handoff is not a review or shipping gate.
267
310
268
311
- Reuse the agreed development worktree and branch, with one owner of product
269
-
edits. Keep one dev server running: `just web` for shared frontend work, or
270
-
`just desktop` when native behavior matters. Vite handles supported frontend
312
+
edits. Keep one dev server running: `BUZZ_DEV_VIEWER= just desktop` for manual
313
+
testing of shipped behavior. `just web` remains useful for browser-only
314
+
diagnostics and fixtures, not acceptance. Vite handles supported frontend
271
315
updates without a package rebuild. State when a reload/restart is needed;
272
316
coordinate native launches with the human rather than restarting their app.
273
317
- Make small, coherent changes and hand them back as **ready to try**, naming
0 commit comments