feat(harness): multi-harness bridge with DSH loopback redirect hardening #9
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
Reference
Ting/workflows#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
Dispatch workflows through DSH and external agent harnesses without weakening loopback transport or accepting unsafe redirects.
Design
Use DSH loopback HTTP without an Origin header under ADR 0003. Disable redirects with
redirect::Policy::none(), reject URL userinfo, support Claude, Pi, and Codex CLI transports, and map validation failures toToolFailureKind::invalid-args.Tasks
ToolFailureKind::invalid-args.Gherkin Specification Delta
must.contracts.ting-workflows.executor.multi-harness-dispatch
Scenario: Dispatch safely across supported harnesses
ToolFailureKind::invalid-args.Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).