~bigbes/sr-ht-dolt · parade

main · last commit 5 hours ago · ti41arbu

← Back to the parade

sr-ht-dolt-44n.4 Copy-ready bd commands on the issue detail pane Past Stand

status: closed P3 task
bd reopen sr-ht-dolt-44n.4
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-08-12T20:11:50Z
Started2026-08-13T05:32:52Z
Updated2026-08-13T05:39:13Z
Closed2026-08-13T05:39:13Z
Description
The page shows work and cannot change it — that is the architecture. Hand over the command instead: a small block under the issue header with the bd commands appropriate to its status (open: --claim, close; in progress: close, --status=open; closed: reopen), each line user-select: all so one click selects a whole command.
Design
docs/DESIGN.views.md ch.6. No JavaScript and no clipboard API. The command names the issue and nothing about paths: this service does not know where the tracker is checked out, and guessing one would be inventing a fact about the reader machine.
Acceptance criteria
The offered commands follow the issue status; nothing is offered that bd would refuse.

Depends on

  • sr-ht-dolt-44n — Beads views, round two: stream, memory, freshness, cross-database parent-child closed

Depended on by

Nothing depends on this issue.

No comments.

Close reason

Landed in 3b06523: status-following bd commands under the issue header, user-select: all per line, no JavaScript. Verified after the fact that 'bd reopen' exists and is the preferred spelling for a closed issue (its help says it is more explicit than 'update --status open' and emits a Reopened event), so the closed branch stands as written.
  • Eugene Blikh added under epic sr-ht-dolt-44n · 2026-08-12T23:11:49Z
  • Eugene Blikh created the issue · 2026-08-12T23:11:49Z
  • Eugene Blikh changed status to in_progress · 2026-08-13T08:32:51Z
  • Eugene Blikh closed the issue · 2026-08-13T08:39:13Z
    Landed in 3b06523: status-following bd commands under the issue header, user-select: all per line, no JavaScript. Verified after the fact that 'bd reopen' exists and is the preferred spelling for a closed issue (its help says it is more explicit than 'update --status open' and emits a Reopened event), so the closed branch stands as written.
Stored rows — what this pane was built from, as read
issues 1 row
id sr-ht-dolt-44n.4
content_hash 740c8403d3b42789698b44c736d7b2512d0e413c0bc926b035a56afed9182726
title Copy-ready bd commands on the issue detail pane
description The page shows work and cannot change it — that is the architecture. Hand over the command instead: a small block under the issue header with the bd commands appropriate to its status (open: --claim, close; in progress: close, --status=open; closed: reopen), each line user-select: all so one click selects a whole command.
design docs/DESIGN.views.md ch.6. No JavaScript and no clipboard API. The command names the issue and nothing about paths: this service does not know where the tracker is checked out, and guessing one would be inventing a fact about the reader machine.
acceptance_criteria The offered commands follow the issue status; nothing is offered that bd would refuse.
notes
status closed
priority 3
issue_type task
assignee NULL
estimated_minutes NULL
created_at 2026-08-12T20:11:50Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-08-13T05:39:13Z
closed_at 2026-08-13T05:39:13Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason Landed in 3b06523: status-following bd commands under the issue header, user-select: all per line, no JavaScript. Verified after the fact that 'bd reopen' exists and is the preferred spelling for a closed issue (its help says it is more explicit than 'update --status open' and emits a Reopened event), so the closed branch stands as written.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at 2026-08-13T05:32:52Z
is_blocked 0
dependencies 1 row
id b3c3899e-00b0-5ac0-a246-6b78d11c19e4
issue_id sr-ht-dolt-44n.4
type parent-child
created_at 2026-08-12T23:11:49Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id sr-ht-dolt-44n
depends_on_wisp_id NULL
depends_on_external NULL
events 3 rows
id 019ff79a-41a2-79b0-9c45-c45f894f9888
issue_id sr-ht-dolt-44n.4
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-08-12T23:11:49Z
id 019ff99b-e62b-742e-b10e-3f524421b71c
issue_id sr-ht-dolt-44n.4
event_type status_changed
actor Eugene Blikh
old_value {"id":"sr-ht-dolt-44n.4","title":"Copy-ready bd commands on the issue detail pane","description":"The page shows work and cannot change it — that is the architecture. Hand over the command instead: a small block under the issue header with the bd commands appropriate to its status (open: --claim, close; in progress: close, --status=open; closed: reopen), each line user-select: all so one click selects a whole command.","design":"docs/DESIGN.views.md ch.6. No JavaScript and no clipboard API. The command names the issue and nothing about paths: this service does not know where the tracker is checked out, and guessing one would be inventing a fact about the reader machine.","acceptance_criteria":"The offered commands follow the issue status; nothing is offered that bd would refuse.","status":"open","priority":3,"issue_type":"task","owner":"bigbes@gmail.com","created_at":"2026-08-12T20:11:50Z","created_by":"Eugene Blikh","updated_at":"2026-08-12T20:11:50Z"}
new_value {"status":"in_progress"}
comment NULL
created_at 2026-08-13T08:32:51Z
id 019ff9a1-b923-7232-997f-da2e69ebcb20
issue_id sr-ht-dolt-44n.4
event_type closed
actor Eugene Blikh
old_value
new_value Landed in 3b06523: status-following bd commands under the issue header, user-select: all per line, no JavaScript. Verified after the fact that 'bd reopen' exists and is the preferred spelling for a closed issue (its help says it is more explicit than 'update --status open' and emits a Reopened event), so the closed branch stands as written.
comment NULL
created_at 2026-08-13T08:39:13Z