@timurproko/a1 0.2.4-dev.667 → 0.2.4-dev.673

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,7 +2,6 @@
2
2
  <style>
3
3
  text{font:500 9.8px 'JetBrains Mono',SFMono-Regular,Consolas,Menlo,monospace;fill:rgb(38,56,210);text-anchor:middle;dominant-baseline:central}
4
4
  .l0{fill-opacity:0.14}.l1{fill-opacity:0.247}.l2{fill-opacity:0.355}.l3{fill-opacity:0.463}.l4{fill-opacity:0.57}.l5{fill-opacity:0.677}.l6{fill-opacity:0.785}.l7{fill-opacity:0.892}.l8{fill-opacity:1}
5
- @media (prefers-color-scheme:dark){text{fill:rgb(166,181,255)}}
6
5
  .f{visibility:hidden}.s{display:none}
7
6
  @keyframes i{from,to{visibility:visible}}
8
7
  @keyframes l{0%{visibility:visible}0.794%,100%{visibility:hidden}}
@@ -2,7 +2,7 @@
2
2
 
3
3
  Local cleanup completes the delivery order in [the archive runbook](openspec-archive-automation.md). For version 3 that is one authorized manual implementation/acceptance/archive merge, read-only verification, remote topic-ref deletion, then safe local cleanup. Legacy versions still require their applicable acceptance-record and automatic archive merges. GitHub Actions never reaches into a developer machine. Local cleanup never publishes archives or merges PRs; `complete`, `retire-redundant`, preview, and queue/watch do not delete remote refs, while explicitly confirmed closed-unmerged `discard` owns only its exact expected-SHA topic-ref deletion.
4
4
 
5
- The implementation is repository tooling, not part of the installed A1 product. It requires Node, Git, and GitHub read access; the explicit closed-unmerged discard operation additionally requires authenticated permission to delete its exact remote topic ref. No product build, dependency installation, interactive UI, or OS-service provisioning is needed. It supports this repository's `origin` on github.com, via HTTPS or SSH.
5
+ The implementation is repository tooling, not part of the installed A1 product. It requires Node, Git, and GitHub read access; the explicit closed-unmerged discard operation additionally requires authenticated permission to delete its exact remote topic ref. No product build, dependency installation, interactive UI, or OS-service provisioning is needed. It supports this repository's `origin` on github.com, via HTTPS or SSH. The repository-local `remote.origin.url` must retain that canonical GitHub spelling; Git may still rewrite the effective transport through `url.*.insteadOf` to select an account-specific SSH host/key. A literal SSH alias remains unsupported because cleanup does not trust external SSH configuration as repository identity.
6
6
 
7
7
  ## Hand-off and sweep: the ordinary agent path
8
8
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@timurproko/a1",
3
- "version": "0.2.4-dev.667",
3
+ "version": "0.2.4-dev.673",
4
4
  "description": "Standalone terminal workspace for supervised native and managed agents",
5
5
  "type": "module",
6
6
  "privateLaunchContract": "neutral-launch-v1",