This repo's own shim claims to be generated from a file that does not exist

[waynesun09]

.github/workflows/fullsend.yaml opens with:

# This file is managed by fullsend. Do not edit it directly.
# Upstream: https://github.com/fullsend-ai/fullsend/blob/main/internal/scaffold/fullsend-repo/.github/workflows/fullsend.yaml

No such file exists. internal/scaffold/fullsend-repo/.github/workflows/ holds the per-org stage workflows (code.yml, dispatch.yml, review.yml, and so on). The per-repo shim template is internal/scaffold/fullsend-repo/templates/shim-per-repo.yaml.

So the header is wrong twice over: it points at a path that does not resolve, and it tells a reader not to edit a file that is in practice hand-maintained, since nothing regenerates it. This repo's shim can therefore drift from the template it is supposed to mirror, and nothing notices.

That drift is not hypothetical. #6959 adds run-name to the template so a follow-up run can be bound to its work item; without the same line here, that binding would have been permanently dead on this repository, because scaffold sync only reaches consumers. It was added by hand in that PR, along with a test that diffs the two.

Proposed change

Either point the header at templates/shim-per-repo.yaml and add a check that this file matches the rendered template, or drop the "managed by fullsend" claim and say plainly that it is maintained by hand alongside the template.

Validation criteria

A change to the shim template that is not mirrored here fails a check, or the header no longer claims a generator that does not exist.

Found while adding run-name to this file in #6959.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 3:10 PM UTC · Completed 3:15 PM UTC

Commit: fecb2f0 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $0.91

[fullsend-ai-triage]

This issue requires modifying .github/workflows/fullsend.yaml (a workflow file). The code agent cannot modify workflow files under current permissions — manual intervention (a human-authored PR) is required.

Related work

• PR feat(dispatch)!: steer the agent run already in flight on work-item updates #6959 (open) already adds a test that diffs the repo shim against the template, which partially addresses the drift-detection side of this issue. However, it does not fix the misleading header. Once feat(dispatch)!: steer the agent run already in flight on work-item updates #6959 lands, the drift check is in place and the remaining work is just correcting the header comments.
• Reconciliation bot shim output diverges from template while claiming sync #2574 covers the same class of problem (provenance header mismatch) for consumer-repo shims generated by the reconciliation bot. The two issues are related but independent — this one is about this repo's own shim.

Proposed test case

func TestShimHeaderUpstreamPathResolves(t *testing.T) {
    content, err := os.ReadFile("../../.github/workflows/fullsend.yaml")
    require.NoError(t, err)

    // Extract the Upstream: path from the header comments
    for _, line := range strings.Split(string(content), "\n") {
        if strings.Contains(line, "Upstream:") {
            // Parse the repo-relative path from the URL
            // Verify the referenced file exists on disk
        }
        if !strings.HasPrefix(line, "#") {
            break
        }
    }
}

---

Labels: Workflow dispatch shim header fix is a chore-type issue in the CI/dispatch component area with low priority since the drift check is already being added in #6959.

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance