Skip to content

feat: artifact browser, universal auto-launch, README rewrite (#50, #51, #52) — v1.7.0#53

Merged
richard-devbot merged 5 commits into
mainfrom
feat/v1.7-end-user
Jun 2, 2026
Merged

feat: artifact browser, universal auto-launch, README rewrite (#50, #51, #52) — v1.7.0#53
richard-devbot merged 5 commits into
mainfrom
feat/v1.7-end-user

Conversation

@richard-devbot
Copy link
Copy Markdown
Owner

Closes #50, closes #51, closes #52.

What — the npm-publish readiness release

#50 — Run artifact & evidence browser

The biggest capture-vs-display gap closed: open any run and read its real deliverables (requirements.json, architecture.md, qa-report, security-review, release-readiness, plan) grouped by stage, plus evidence records.

  • GET /api/artifact?run&path — strictly sandboxed (run via known roots, path must stay inside the run dir, text-only, 512KB cap). Live-tested: real content served; escape → 403; binary → 415.

#51 — Universal dashboard auto-launch

'The dashboard should come live when a session starts' — for every framework:

  • rstack-agents hub: register project + health-check + spawn + open (the universal hook)
  • Operator: Python adapter launches the hub on extension load (best-effort, RSTACK_NO_BUSINESS_HUB=1 opts out)
  • Claude Code: init writes a SessionStart hook when settings.json is absent (mergeable snippet otherwise)
  • Pi: already native; auto-launch now opens the browser even when the hub was already running

#52 — README rewrite

705 → 149 lines. User-first, honest ('what gets recorded and what doesn't' incl. the token/cost limitation), removed phantom commands and contributor walls of text.

Verification

  • 101/101 tests, lint clean, Python adapters syntax-checked
  • Artifact API live-tested on real run data incl. both sandbox rejections
  • hub command smoke-tested

Release

v1.7.0 + CHANGELOG.

🤖 Generated with Claude Code

richardsongunde and others added 4 commits June 2, 2026 19:26
…for every framework (#51)

- 'rstack-agents hub': health-check :3008, spawn detached if down, open
  browser, register the project — the universal session-start hook
- auto-launch now opens the browser even when the hub is already running
  (a session start should always surface the dashboard)
- Operator adapter launches the hub when the extension loads (same contract
  as Pi; best-effort, RSTACK_NO_BUSINESS_HUB=1 opts out)
- init --framework claude-code writes a SessionStart hook into
  .claude/settings.json when absent; otherwise leaves a mergeable snippet

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…roduced, in the UI (#50)

- runs index their deliverables (plan.md, context.md, artifacts/ top-level +
  per stage) with sizes
- GET /api/artifact?run&path — strictly sandboxed: run resolved via known
  project roots, resolved path must stay inside the run dir, text extensions
  only, 512KB cap (escape attempts 403, binaries 415)
- Run drawer: Deliverables grouped by stage with click-to-read content viewer;
  Evidence section listing the latest validation records

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
705 → 149 lines. What RStack is, 2-minute install per framework, the
dashboard + Studio 3D, approvals/policy, webhooks, an honest 'what gets
recorded (and what doesn't)' section incl. the token/cost limitation, CLI +
env reference, layer map. Removed contributor release walkthroughs and
commands that no longer exist (rstack-agents business).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… release

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@qodo-code-review
Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

…letes work found in working tree)

Found uncommitted in the working tree (parallel session) and half-swept into
d3a223f by a directory-level git add — landing it whole:
- Only configured managers may resolve approvals: policy.json managers[] or
  RSTACK_MANAGER_USERS env; sdlc_approve + dashboard resolution both enforce
- Blocked gates enqueue actionable approval requests with stable gate ids
  (gate:<run>:<task>:<artifact>) → they appear in the dashboard queue with
  approve/reject buttons; sdlc_approve resolves the matching queue entry
- Run approvals sync helper + queue rewritten as idempotent upserts
- Tests updated for queue ids and manager policy

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@richard-devbot richard-devbot merged commit 218c9c4 into main Jun 2, 2026
6 checks passed
@richard-devbot richard-devbot deleted the feat/v1.7-end-user branch June 2, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants