Customer issue report

Christoph's reported issues

What has been resolved, what is already running in production, and what the team will do next. “Deployed” is kept separate from “verified by Christoph” so the remaining acceptance work is visible.

Status checked 15 September 2026
Done
Core conversation failures are repaired

Mail delivery, field-guard context, lost replies, and top-level schema requirements are settled.

Verify now
Recent fixes are in production

Billing access, old-agent upgrades, schema constraints, and several Slack paths need final real-account checks.

Next
Slack actions are the first build item

Custom button dispatch remains the main unresolved product blocker, followed by CLI release and account cleanup.

Rough timeline

The dates show delivery order, not promised completion dates. Verification steps depend on access to the preserved account and agent.

Completed and confirmed

The first blockers were closed

  • Login mail now reaches the preferred address.
  • AAF-060: field guards can inspect the current turn's tool context.
  • FEEDBACK 50: completed turns post their replies.
  • AAF-061: Christoph corrected the report; top-level required is enforced.
  • AAF-058 and AAF-063 were withdrawn after fresh reproductions.
Built and deployed

The next repair set reached production

  • AAF-067: Slack installation guidance and actionable channel errors.
  • AAF-069: Slack command event filters now match correctly.
  • AAF-070: early command acknowledgement and supported delayed replies.
  • Agent message schemas retain minimum and minItems while provider requests use a compatible subset.
  • Failed participate turns now leave a safe, durable Activity Feed error.
  • AAF-072: login now enrolls the default plan and exposes card setup to the first administrator.
  • AAF-073: existing agents can recover child provenance without replacing agent identity.
Verification

Confirm the production behavior on preserved state

  • Sign in again, open card setup, save a payment method, and make an authenticated CLI read.
  • Dry-run one preserved old agent, apply the upgrade, then confirm its ID, tool, threads, memories, and four routines remain intact.
  • Retest a participate routine using minimum and minItems.
  • Exercise the documented Slack invite, filtered-command, loading-message, and final-replacement paths in a real workspace.
Build next

Finish the remaining product work

  • AAF-068: admit documented customer action IDs so Slack button clicks reach waiting routines.
  • AAF-065: publish the already-merged organization-scoped script update in a new CLI release.
  • Move the developer account to the preferred email after identity and collision checks.
  • Add the cross-company work-item guide to navigation and answer symmetry and fan-out directly.
  • AAF-066: reproduce the app-level Slack return-to-root flow if that path is still needed.
Record reconciliation

Recover four report descriptions from the original attachment

  • AAF-059, AAF-062, AAF-064, and AAF-071 cannot yet be mapped safely from the retained email text.
  • The team will recover the already-sent issue attachment internally rather than ask Christoph to reproduce or resend it.

Issue reference

A compact view of every AAF identifier mentioned in the September email batch.

ReferenceStatusCurrent position
AAF-058WithdrawnNo longer reproduced.
AAF-059Needs source matchDescription is only in the missing attachment.
AAF-060Verified fixedTool context is available to opted-in field guards. Change 12898.
AAF-061CorrectedTop-level required is enforced; the earlier result was caused by a separate schema failure.
AAF-062Needs source matchDescription is only in the missing attachment.
AAF-063WithdrawnSolution validation already reports the tested version mismatch.
AAF-064Needs source matchDescription is only in the missing attachment.
AAF-065Release pendingThe scoped update is merged, but the public CLI release still predates it. Change 13332.
AAF-066Partially answeredThe supported per-org setup is documented; the app-level root redirect was not reproduced. Change 13305.
AAF-067VerifyHuman channel invitation is the intended step; clearer errors are deployed.
AAF-068Open blockerCustom Slack button actions are still rejected before routine dispatch.
AAF-069DeployedCommand filters are fixed; a live Slack retest remains. Change 13390.
AAF-070DeployedEarly acknowledgement and delayed responses are supported; live rendering remains to be checked.
AAF-071Needs source matchThe email says it reproduced twice, but the report body is unavailable.
AAF-072DeployedFresh login, card setup, and CLI access need customer confirmation. Change 13673.
AAF-073DeployedOne preserved agent must be upgraded and checked in production. Change 13714.

“Deployed” means the relevant production rollout completed successfully. It does not mean Christoph has repeated the original scenario yet.