v3 crash recovery's progress line breaks --json stderr: a failing command that recovered prints text before its JSON error (regression from #3363 / #3893)
swamp-club.com/cve/tailworm states two things its sources do not say: finding 5's memory growth and no exploitation in the wild
@swamp/cve/tailworm: after mitigate caps headscale, the rescan still tells you to set MemoryMax and Restart=always
WS handshake drops the port from the Origin, so a --trusted-hosts entry with a port never matches (follow-up to #1840)
A workflow step's method output is invisible to `data query` and `data list`, and the method summary's retrieval command returns an older run's data
Skill propulsion rule is silent when no transition is satisfied because stage work is outstanding
Docs: document workflow evaluation counts and subphase timings
package.json mode: no loose-specifier warning for a range push ships as the exact installed version
extension fmt (and any command) creates or rewrites deno.lock when the extension lives in the repo's loaded extensions/ dir
serve shutdown does not wait for worker status writes, and its listener accepts workers after the gateway is disposed
Registry rescore: secret-safe-docs passes a secret README line on versions whose stored metadata predates the sensitive flag (follow-up to #3783)
stagecraft: rename work mode `method` to `behavior`, matching swamp's rename of models to behaviors
invalid-acceptance refuses an apostrophe in a swamp-quality-ignore reason and leaves the finding unresolved
extension quality --json reports percentage but not the grade that extension info and the registry show
auth token create --json fields key and signinToken are undocumented; no token-mode service setup page
trigger.schedule is evaluated in the serve host's local time zone, with no zone field and no doc saying so
workflow validate/run say "Workflow not found" for a file that doctor workflows explains is misnamed
telemetry stats says "No telemetry data found" right after successful sends; say the spool is empty because it flushed
Homebrew tap README omits the brew trust step Homebrew 7 requires, so brew install swamp refuses the formula
Docs: publish typed-secrets Phase 4.6 expression and delivery semantics
Extension registry page: a supported way to include media (images) in the README
CEL: data.latest(...).version is a double, but data.version() only accepts int, so "version - 1" fails at run time
workflow resume --run refuses workflows with the same step name in two jobs, though validate and run accept them
Update public OpenTelemetry manual for remote waterfalls and execution metrics (#3786)
Share the extension quality rubric between the swamp CLI and swamp-club instead of mirroring it
Server-driven warning and info messages to CLI users, targeted by swamp version (exploration)
Serve: delegate namespace-scoped extension pulls and reload without granting administrator access
workflow cancel --server ignores --ca-cert and SWAMP_CA_CERT
Preserve active worker execution across serve restarts and upgrades; reconnect and reattach dispatches
v3: chunk durability barrier costs a full drive-cache flush per command on macOS; use an ordering barrier
vary/forEach object values with no key/name/id produce data names Windows refuses
issue-lifecycle start drops issue comments: context.comments is always empty
swamp core: a non-string sensitive value reads back as a JSON string
Generated vault keys carry raw data-name and vary characters that strict vault providers reject
bundleExtension 'bundles on different caches do not wait for each other' test fails under CPU load
extension install and extension pull leave different bundles for the same extension version
Registry drops contentMetadata.extensions (method grafts) at confirm-push
Multi-model skill eval: gpt-5.4 and gemini jobs fail preflight every run (OpenAI credits exhausted, Google API key invalid)
local_source_failed drops the indexing error: a transient local extension failure leaves no cause (follow-up to 1672)
Finer-grained method locking: a long-running method on one definition blocks unrelated objects managed by the same definition
Surface (or warn about) values a model method returns besides dataHandles, with sensitive-field support
workflow placement: run a workflow transparently on a specified host, local or via swamp workers (incl. nested child workflows)
issue-lifecycle: pr_merged and ship report success and advance the phase when swamp-club is unreachable, writing nothing upstream
auth login leaves auth.json apiKey empty and stores the key only in ~/.config/swamp/api-key, which the auth gate never reads
swamp-extensions CI: Review Integrity explains a stalled or failed audit (streamed progress, timeout, did-not-finish comment)
Workflow run cancellation on concurrency-key conflict
Read non-string sensitive resource fields back with their type
Run index repair-by-stat misses an in-place, same-size record rewrite that restores mtime within the same second as its entry: ctime is reported in whole seconds
Configurable storage tiers: runs, outputs, data versions and audit move through an ordered list of user-defined tiers, and stay queryable across them
A global argument that evaluates to swamp-namespace expression text is silently dropped, and literal() cannot pass it through
serve: the per-IP WebSocket burst limit can't be configured, so workers behind one NAT IP throttle each other
extension pull: safety analysis scans the bundle the extension runs
S3-backed serve: a poll that pulls one file invalidates the whole data catalog, so the next query re-reads every version
swamp-extensions: CI check that every manifest declares license: and ships a LICENSE file
extensions_search index is never created if the first attempt fails, until the process restarts
S3/GCS datastore sync: shared sync service lets one sync clear another's dirty marks and pull over unpushed files
swamp-uat: the SIGTERM drain test does not check that the run succeeded
stagecraft: a factory-wide read of work items waiting on a person (no studio, no per-item status loop)
stagecraft: rebind a work item to another tracker (mirrored built-in tickets to Jira)
s3-datastore: first push on a fresh cache prints 'Index merge failed' for a missing local .datastore-index.json
swamp-extensions: use explicit npm:/jsr: specifiers in root extensions/models
stagecraft: studio state_test 'after its event stream reconnects' is timing-flaky under load
Activity projector fails with ZooKeeper "Bad version" error on swamp.score_grants during keeper instability
s3-datastore: model-scoped pullChanged lists and walks the whole namespace
extension safety analyzer does not warn on node:child_process or cluster subprocess spawning
extension push: a swamp-quality-ignore directive after a comment holding an apostrophe is silently ignored
Model types: decide whether names like @/@x/y or a+b/c should be legal (type grammar)
seed:collective cannot produce a superseded personal trial or a returned trial, so the UAT cannot cover them
serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once
extension push: accept attestation-backed adversarial-review evidence (lookup by extension and content hash), generated provenance, and carry the evidence to the registry at confirm (design: Lab #3023)
Decide a stricter naming rule for workflow step and job names
s3-datastore/serve: readResource without a version returns an older version; the latest marker is rewritten backwards
Publish agent-facing projections of the manual: /llms.txt, .md pages, and llms-full.txt
Let agent-runner drive more agent CLIs (Kilo Code and others)
s3-datastore: every fast-path miss re-downloads every _index shard, so a busy serve pulls the whole index every poll (~230 GB/day S3 egress)
Feedback: Swamp as an approval-gated control plane for a small fleet
Tracking: test baseline required before the datastore refactor (commit-log design)
serve: define and supply the collective and owner grant condition variables
No first-class workflow primitive for spawning a permission-scoped agent session
Decorative animations outside the Lab still repaint on the main thread
s3/gcs datastore: pullChanged overwrites dirty, unpushed cache files
Codegen/AWS: create-only required fields block list/get/delete in generated AWS models
End a collective's trial when it begins a paid subscription
s3-datastore: SWAMP_S3_REQUEST_TIMEOUT_MS does not appear to apply to ListObjectsV2 during pull
s3-datastore: S3Lock.acquire overshoots maxWaitMs by up to a full backoff interval
s3-datastore: a model-scoped pull still lists, walks and indexes the whole namespace
Run the web dashboard locally from the CLI without swamp serve
extensions: cold-path catalog rebuild skips sources whose type is not a string literal, dropping them for one process lifetime
serve: rotate the external token-secrets key
Link each swamp-club panel to its manual page with a header DOCS link
managedConfig: extension lockfile writes lose updates, and auto-resolved installs never reach the shared lockfile
Generated @swamp/aws StateSchemas mark conditional and create-only properties as required, producing schema warnings on every read
workflows: a nested workflow step should inherit the caller's placement when the child declares none
Supported vault-write API for extension model methods (per-instance vault target)
serve: after lazy hydration, scoped poller pulls never take the fast path, and the login mint waits behind them on the sync gate
datastore extensions: full pushes re-hash every pulled file on every run because index mtimes never match pulled copies
Extension catalog caches a datastore bundle with an empty type, so the repo fails with Unknown datastore type when addressed by its realpath
Let a method inside serve start a workflow run: context.runWorkflow
s3/gcs datastore: no safe recovery when _meta.json v2 lists a shard missing from the bucket
worker secret allowlist rejects caller-chosen vault references resolved at run time (method args carrying {vaultName, secretKey})
serve: default placement for steps that declare none (so one workflow runs both locally and via workers)
s3-datastore: per-datastore AWS profile, so a serve audit store can use different credentials from the main datastore
s3/gcs-datastore: clean up data left behind by deletes that silently no-opped before the swamp-club#2249 fix
Expose Swamp as a REST/OpenAPI endpoint (for GPT Actions and other REST clients)
Promote CodeBuddy and WorkBuddy from custom-tool configs to first-class Swamp clients
s3-datastore: documented offline behaviour is unreachable — lock acquire fails closed before pull, while a mid-run outage exits 0 with the data stranded
Relationships
#1908 Add safe per-work-item workspace preparation
Opened by funsaized · 8/30/2026· Shipped 9/28/2026
Provide an official idempotent method that fetches an exact base ref, creates or safely reuses one verified Git worktree and branch per work item, refuses unrelated or overlapping paths, preserves expected dirty rework state, and returns subjectRoot, branch, and baseCommit.
Upstream repository: https://github.com/swamp-club/swamp-extensions
Environment
- Extension:
@swamp/git@2026.08.25.1 - swamp:
20260828.231706.0-sha.ca29674e - OS:
darwin(aarch64) - Deno:
2.8.3 - Shell:
/bin/zsh
Shipped
Click a lifecycle step above to view its details.
stack72 commented 9/28/2026, 9:49:49 PM
Thanks @funsaized for reporting this! We shipped: Add ensure_worktree and verify_worktree to @swamp/git and fix remove_worktree path comparison. ensure_worktree fetches an exact base ref race-free, creates or safely reuses one verified worktree and branch per work item inside an optional bounded root, refuses unrelated or overlapping paths, preserves in-progress rework, and returns subjectRoot, branch, and baseCommit. verify_worktree is a read-only fail-closed check of an existing worktree against expected branch, base lineage, root, and remote.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.