Fix forgejo bundle metadata selection #1058

Merged

coilysiren merged 2 commits from issue-1049 into main

2026-07-10 21:03:59 +00:00

coilyco-ops commented

2026-07-10 17:36:20 +00:00

Member

Selects the flat bundle's Forgejo ops entrypoint from ward.bundle.kdl metadata instead of a hardcoded consumer guardfile filename, keeping a compat path for guardfile.forgejo.kdl bundles.

Repaired per operator dispatch on #1058: merged current main into the branch, preserved main's post-ward#1009 structure (no .ward/ward-kdl/ file restored - that tree is byte-identical to main), and kept only this PR's consumer-code change. The earlier do-not-merge hold was overridden by that dispatch.

Related rework: #1064. Operator-surface follow-up that shipped PR body edits: #1062.

closes #1049

ward.workflow: pull-request-and-merge

Selects the flat bundle's Forgejo ops entrypoint from `ward.bundle.kdl` metadata instead of a hardcoded consumer guardfile filename, keeping a compat path for `guardfile.forgejo.kdl` bundles. Repaired per operator dispatch on #1058: merged current `main` into the branch, preserved main's post-ward#1009 structure (no `.ward/ward-kdl/` file restored - that tree is byte-identical to main), and kept only this PR's consumer-code change. The earlier do-not-merge hold was overridden by that dispatch. Related rework: #1064. Operator-surface follow-up that shipped PR body edits: #1062. closes #1049 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-10 17:36:20 +00:00

fix(config): expose forgejo bundle metadata

test / test (pull_request) Successful in 26s

Details

f6db5e80e8

coilyco-ops referenced this pull request

2026-07-10 17:45:34 +00:00

Add ward ops forgejo pr edit #1062

coilyco-ops referenced this pull request

2026-07-10 17:46:06 +00:00

Make WARD_CONFIG_REF bundle loading independent of consumer KDL filenames #1064

coilyco-ops commented

2026-07-10 20:21:28 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-claude-ward-1058 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness claude (reserved 2026-07-10T20:21:27Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1058 · branch issue-1058 · harness claude · workflow pull-requests-and-merge
Run: engineer-claude-ward-1058 · ward v0.600.0 · dispatched 2026-07-10T20:21:27Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.600.0).

— Claude (she/her), via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-claude-ward-1058` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness claude` (reserved 2026-07-10T20:21:27Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1058` · branch `issue-1058` · harness `claude` · workflow `pull-requests-and-merge` - **Run:** `engineer-claude-ward-1058` · ward `v0.600.0` · dispatched `2026-07-10T20:21:27Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.600.0). </details> </details>  — Claude (she/her), via `ward agent`

coilyco-ops added 1 commit

2026-07-10 20:29:54 +00:00

Merge remote-tracking branch 'origin/main' into issue-1049

test / test (pull_request) Successful in 30s

Details

42e7a9a52f

Resolve the configsource conflicts by keeping main's post-ward#1009
structure and this PR's bundle-metadata selection: the flat bundle's
Forgejo ops entrypoint now comes from ward.bundle.kdl metadata instead
of a hardcoded consumer guardfile filename. The test-side git-ref
harness (makeTestConfigBundleRepo) stays deleted per main; the neutral
and compat bundle fixtures carry the coverage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>