Skip to content

docs(openspec): archive bun trust rollback change #404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Drswith merged 1 commit into from
Jul 2, 2026
Merged

docs(openspec): archive bun trust rollback change #404

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 ...bun-install-trust-rollback/.openspec.yaml → ...bun-install-trust-rollback/.openspec.yaml
View file
Open in desktop
File renamed without changes.
0 .../fix-bun-install-trust-rollback/design.md → ...-fix-bun-install-trust-rollback/design.md
View file
Open in desktop
File renamed without changes.
0 ...ix-bun-install-trust-rollback/proposal.md → ...ix-bun-install-trust-rollback/proposal.md
View file
Open in desktop
File renamed without changes.
0 ...trust-rollback/specs/agent-update/spec.md → ...trust-rollback/specs/agent-update/spec.md
View file
Open in desktop
File renamed without changes.
0 ...s/fix-bun-install-trust-rollback/tasks.md → ...2-fix-bun-install-trust-rollback/tasks.md
View file
Open in desktop
File renamed without changes.
12 changes: 11 additions & 1 deletion openspec/specs/agent-update/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ When Quantex performs a grouped managed batch update for an installer type, it S

### Requirement: Bun-managed updates MUST trust requested blocked lifecycle scripts across platform path styles

The agent update system SHALL recognize Bun global untrusted package output for requested managed packages regardless of whether Bun prints `node_modules` paths with POSIX or Windows separators. When the untrusted probe cannot be read after a successful Bun global install or update command, Quantex SHALL NOT report that managed operation as successful.
The agent update system SHALL recognize Bun global untrusted package output for requested managed packages regardless of whether Bun prints `node_modules` paths with POSIX or Windows separators. When the untrusted probe cannot be read after a successful Bun global install or update command, Quantex SHALL NOT report that managed operation as successful. When trust verification fails after a successful Bun global **install** command, Quantex SHALL roll back the newly added package before reporting install failure.

#### Scenario: Trusting a requested scoped package from Windows Bun output

Expand All @@ -168,6 +168,16 @@ The agent update system SHALL recognize Bun global untrusted package output for
- THEN Quantex reports the managed operation as failed
- AND it does not claim the install or update succeeded without completing trust verification

#### Scenario: Rolling back a Bun install when trust verification fails

- GIVEN a Bun-managed install requested one or more package names
- AND `bun add -g` exits successfully for those packages
- AND Bun trust verification fails afterward
- WHEN Quantex evaluates the managed install outcome
- THEN Quantex removes the packages that were just added with `bun remove -g`
- AND it reports the Bun install attempt as failed
- AND a subsequent fallback install method may run without leaving a duplicate Bun global install behind

#### Scenario: Skipping untracked PATH detections during batch update

- GIVEN an agent binary is detected in `PATH`
Expand Down
Loading