Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

F-027 A3 — Change log, run authority and "Ask me first"

Chiusa
#403 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@PelikanFix16 ci sta già lavorando.

Dal 9/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Slice A3 of F-027 (founder direction 2026-10-09; contract PR #401). The AST criteria referenced below are defined there and are this issue's acceptance criteria.

  • Scope. The /mcp effect path for a run token classifies each call as applied,
    waiting, suggestion or refused (AST-5 table and lists), records it in the change
    log in the same transaction, and returns a plain tool result ("Waiting for Ada's
    OK" or the applied object). Receipts record owner_request. Waiting changes:
    owner-only API to Apply, Apply all, Not now; re-execution with every check and
    version comparison; 7-day expiry. The conversation card "Wants to: …".
  • Files. app/apps/server/src/agent-connection/action-execution.ts,
    work-actions.ts, doc-actions.ts, map-actions.ts, conversation-actions.ts;
    app/packages/core/src/assistant/changes.ts; app/apps/web/src/assistant/
    (card).
  • Migration 0078 assistant_changes (run, workspace, project, object type and
    id, operation, state CHECK applied|waiting|applied_after_wait|not_now|expired| undone|refused, prepared command JSON for waiting rows with a size CHECK, before
    and after versions, receipt, decided by and at).
  • Tests. AST-4.3, AST-5.2 to AST-5.8, AST-6.5, AST-6.7, AST-9.2; the live-Wiki
    deferral with PR #389's session signal faked; waiting changes moving to Inbox with a
    fixed clock.
  • Depends on. A1, A2.

Rules: Docker tests with fakes/mocks only (no real vendor account, key or spend); final design (Prostota) components; UX reviewed against F-027's journeys by an independent evaluator in the running app.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
19h 44m
PR unite (30g)
367

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.