Skip to content

RE-027 Generalize crash-mode auto-exit beyond TTY detection #219

Open
Open
RE-027 Generalize crash-mode auto-exit beyond TTY detection#219
Labels
lane:cool-ideasInteresting but not committed work.legend:reRuntime Engine work.priority:mediumMedium priority.type:enhancementFeature or improvement.
Milestone
v10.0.0

Description

@flyingrobots
flyingrobots
opened on Jun 1, 2026

Requested classification

  • Source lane: inbox
  • Applied lane label: lane:inbox
  • Legend label: legend:re
  • Type label: type:enhancement
  • Priority label: priority:medium
  • Initial milestone triage: Beyond
  • Source file: docs/method/backlog/inbox/RE_re-027-generalize-crash-mode-auto-exit-beyond-tty-detection.md

Finding

This backlog evidence card existed in the repository but was not represented as a canonical GitHub Issue. Importing it makes GitHub Issues the live tracker while preserving the filesystem card as evidence lineage.

Hill

A Bijou maintainer can triage, pull, split, or close RE-027 from GitHub without relying on local filesystem spelunking or chat memory, while still having a direct link back to the original Method backlog evidence.

Sponsored perspectives

  • Sponsored Human: Bijou maintainer or contributor deciding whether this card belongs in v6, v7, or a later horizon.
  • Sponsored Agent: Implementation, review, or triage agent using GitHub Issues as the canonical queue and source files as evidence.

Current repo note

Verified against main at edf123f5 on 2026-06-01.

Import status: Open after backlog import; milestone assignment is initial triage and can be reshaped.

Scope

  • Preserve the original backlog card in GitHub Issues.
  • Keep the issue labeled with its source Method lane.
  • Use the milestone as the initial release-horizon triage signal.
  • Split or reshape this issue if implementation scope is broader than one cycle.

Out of scope

  • Treating the source backlog wording as immutable implementation design.
  • Expanding this card beyond the imported problem without a design or triage comment.
  • Closing implementation work without evidence.

Acceptance criteria

  • Source backlog card is visible in GitHub Issues.
  • Source lane label and initial milestone triage are applied.
  • Work is either pulled into a cycle, split into sharper issues, or moved to a different milestone with a comment explaining why.
  • Closing evidence links tests, playback, docs, retro/closeout, and PR or explicit no-code rationale.

Expected evidence

Tests

Name the deterministic test command, failing-before-fix reproduction, or reason no code test applies when this card is pulled.

Playback

Name the human-visible playback, demo, transcript, or reproduction that proves the result.

Docs

Update affected docs, DOGFOOD surfaces, issue metadata, and changelog entries when behavior or release posture changes.

Retro / Closeout

Record closeout in the issue, linked PR, committed retro, or explicit no-code close reason.

Method artifacts

  • Design: docs/method/backlog/inbox/RE_re-027-generalize-crash-mode-auto-exit-beyond-tty-detection.md is the imported backlog evidence; create or link docs/design/<LEGEND>-<issue>-<slug>.md if the work needs a design record.
  • Witness: Pending unless the issue is closed by import evidence.
  • Retro: Pending unless the issue is closed by import evidence.
  • PR: Link before closing implementation work.

Imported source card

RE-027 Generalize crash-mode auto-exit beyond TTY detection

The current crash-mode fix auto-exits when stdinIsTTY is false. Follow up by making crash-mode exit policy depend on actual input availability or host capabilities, so worker/IPC transports can explicitly opt in to crash-surface interactivity without being tied to process TTY heuristics.

Triage rule

Initial triage is Beyond. Move this issue when release planning decides it belongs in a different horizon, and leave a comment explaining the decision.

Activity

  1. flyingrobots
    added this to the Beyond milestone on Jun 1, 2026
  2. flyingrobots
    added
    lane:inboxRaw intake; needs triage before work starts.
    priority:mediumMedium priority.
    type:docsDocumentation work.
    legend:reRuntime Engine work.
    on Jun 1, 2026

  3. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    coderabbitaibot
    on Jun 1, 2026 – with coderabbitai
    🔗 Related PRs

    #60 - feat(runtime): RE-007 migrate framed shell onto runtime engine seams [merged]
    #511 - Design Geordi native GPU host for Bijou cell buffers [open]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  4. flyingrobots
    added
    type:enhancementFeature or improvement.
    and removed
    type:docsDocumentation work.
    on Jun 1, 2026
  5. flyingrobots
    modified the milestones: Beyond, v10.0.0 on Jul 5, 2026

  6. flyingrobots commented on Jul 5, 2026

    @flyingrobots
    flyingrobots
    on Jul 5, 2026
    OwnerAuthor

    Backlog release triage: assigned to v10.0.0.

    Reason: Crash-mode auto-exit generalization is runtime host behavior follow-through.

    This keeps the GitHub issue tracker aligned with the expanded post-v8 release horizon instead of leaving active work in Beyond or without a milestone.

  7. flyingrobots
    changed the title [-][Beyond] RE-027 Generalize crash-mode auto-exit beyond TTY detection[/-] [+]RE-027 Generalize crash-mode auto-exit beyond TTY detection[/+] on Aug 10, 2026
  8. flyingrobots
    added
    lane:cool-ideasInteresting but not committed work.
    and removed
    lane:inboxRaw intake; needs triage before work starts.
    on Aug 10, 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

    lane:cool-ideasInteresting but not committed work.legend:reRuntime Engine work.priority:mediumMedium priority.type:enhancementFeature or improvement.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions