Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#403 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 9, 2026.

Assessment

This issue has not been assessed yet.

Description

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.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
13h 27m
Merged PRs (30d)
224

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.