Skip to content

✨ feature[v6]: Dashboard Chat: report scaffold file count and download path on inception approve #18259

Closed as not planned

Description

@kanrenibm

Use case

An operator who runs Inception only through chat is never told that a scaffold exists or how to get it.

Run on a spoke (greenfield, !inception start → 7 answers → !inception approve):

  • After ✅ Submitted 7 answers., chat shows only agent status lines ([brainstorm] Completed, [supervisor] Completed). It does not say the scaffold is ready or that !inception approve is the next step.
  • The engine reached phase scaffold at 04:30:40 (-05:00, hive log: inception watcher: facts extracted, advancing to scaffold). GET /api/inception/scaffold then returned 13 files.
  • !inception approve replied with one line: ✅ Inception approved and brainstorm re-paused. No file count. No download path.
  • !inception state in phase scaffold or complete has no scaffold line. By the code it prints the idea, Moving on with N of M answers. and Facts recorded: N (inception.go:176-185). Not run during this test.

Environment:

Code:

  • src/pkg/chat/inception.go:123-131 returns the fixed approve line.
  • cmdInceptionState (inception.go:154-190) never reads the scaffold.
  • No code under src/pkg/chat calls /api/inception/scaffold or /api/inception/download.

Affected: operators using the chat-only Inception flow (#7563 "dashboard-optional operation", #9735 row "Inception via chat").

Logs Taken during the test :

logs.zip

Proposed solution

Chat should report what was produced and where to get it.

  1. After !inception approve succeeds and a scaffold exists, the reply adds the file count and the download path, for example:

    📦 Scaffold ready: 13 files generated.
    ⬇️ Download: /api/inception/download
    

    If no scaffold can be read, the reply stays as it is today.

  2. !inception state in phase scaffold or complete adds a scaffold line with the file count and the download path.

  3. When the phase changes to scaffold, chat posts one line: the scaffold is ready, review it, then send !inception approve.

Alternatives considered

  • Docs only. docs/inception.md:102-103 and :169-173 already describe review and download. An operator in chat does not read them at that point.
  • List the file paths in chat. About 13 lines per call. The count and the download path are enough.
  • New command such as !inception download. Larger surface than a reply line. The operator still has to know the command exists.

Scope and compatibility

  • Target branch or version: v6 only. Tested on fd020b3; src/pkg/chat unchanged at 15a6de7. The default branch v5 has no src/pkg/chat/inception.go.
  • Operator impact: extra lines on !inception approve, !inception state and one phase-change message. No new command, flag or config.
  • Contributor/agent impact: reply text in src/pkg/chat. GET /api/inception/scaffold does not change the phase (docs/inception.md:169).
  • Migration or backwards-compatibility concerns:
    • The first line of the approve reply is unchanged. docs/v6-readiness-runbook.md:514 still holds.
    • Only inception.go:131 and that runbook line contain the approve text.
    • The dashboard shows Sessions instead of the Inception panel when sessions are enabled (agent-detail.js:242). The sessions.js file has no reference to /api/inception/download. The message should name the API path and not a tab.

Additional context

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 15, 2026
  2. changed the title [-]✨ feature: Dashboard Chat: report scaffold file count and download path on inception approve[/-] [+]✨ feature[v6]: Dashboard Chat: report scaffold file count and download path on inception approve[/+] on Nov 15, 2026
  3. added
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Nov 15, 2026
  4. hivecommons-hive commented on Nov 15, 2026

    @hivecommons-hive
    Contributor

    Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label triage/accepted (configured in issue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.

  5. added
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    stage/stalledIn its current stage longer than expected
    on Nov 15, 2026
  6. clubanderson commented on Nov 17, 2026

    @clubanderson
    Member

    Closing as obsolete. #18419 (merged 2026-11-16) retired the inception API, watcher and scaffold generator that this report exercised; /api/inception/approve and /api/inception/scaffold now return "gone", and inception runs as Spek sessions. Thanks for the careful, detailed report, it was useful while the old flow existed. If the Spek session flow has a similar gap in reporting what it produced, please open a new issue against it.

  7. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor

    @kanrenibm this issue was closed by @clubanderson as not planned.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

  8. removed
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    stage/stalledIn its current stage longer than expected
    on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions