Configure warded git committer identity #504

New issue

Closed

opened 2026-07-13 18:59:18 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-13 18:59:18 +00:00

Member

Configure the warded-agent git committer identity to the coilyco-ops bot instead of letting ward fall back to the example bot identity.

Problem:

Warded runs are currently able to fall back to an example bot committer identity.
agentic-os should configure the coilyco deployment ward overlay so commits made by warded containers use the coilyco-ops bot identity.
.ward/agents.kdl currently has attribution name=coilyco-ops email=coilyco-ops@coilysiren.me, but that is not sufficient if git's committer identity still falls through to ward's example default.

Context already checked from this read-only surface:

.ward/agents.kdl contains only the attribution default for coilyco-ops.
docs/dev-base-git-identity.md claims ward sets user.email at system scope to coilyco-ops@coilysiren.me, but the live behavior reported by Kai says the committer identity still falls back to the example bot.
The fix belongs in the coilyco ward config authored by agentic-os, unless inspection proves ward lacks a config knob. If ward lacks the knob, file the paired ward issue and make the aos change consume the new knob once available.

Required fix:

Find the ward config key or env knob that controls git committer identity for warded containers.
Set the deployment default to:
- name: coilyco-ops
- email: coilyco-ops@coilysiren.me
Keep per-agent self-name behavior only where it is intentionally author-name display behavior. The bot identity must be the committer/account-linking identity, not an example fallback.
Update docs/dev-base-git-identity.md if its current explanation is stale or incomplete.
Add or update tests so a future config change cannot regress to an example identity. Do not assert unrelated KDL content; test the owning identity field or the rendered/loaded config behavior.

Validation:

Run ward doctor.
Run relevant tests through ward.
Verify a resolved warded launch or equivalent config render no longer contains the example bot identity and resolves the git committer name/email to the coilyco-ops bot.

Acceptance:

The coilyco ward overlay explicitly configures git committer identity for warded containers.
The example bot identity is not present in the resolved launch identity path.
Commits from warded containers attribute to coilyco-ops as committer/account identity.

Configure the warded-agent git committer identity to the coilyco-ops bot instead of letting ward fall back to the example bot identity. Problem: - Warded runs are currently able to fall back to an example bot committer identity. - `agentic-os` should configure the coilyco deployment ward overlay so commits made by warded containers use the `coilyco-ops` bot identity. - `.ward/agents.kdl` currently has `attribution name=coilyco-ops email=coilyco-ops@coilysiren.me`, but that is not sufficient if git's committer identity still falls through to ward's example default. Context already checked from this read-only surface: - `.ward/agents.kdl` contains only the attribution default for `coilyco-ops`. - `docs/dev-base-git-identity.md` claims ward sets `user.email` at system scope to `coilyco-ops@coilysiren.me`, but the live behavior reported by Kai says the committer identity still falls back to the example bot. - The fix belongs in the coilyco ward config authored by `agentic-os`, unless inspection proves ward lacks a config knob. If ward lacks the knob, file the paired ward issue and make the aos change consume the new knob once available. Required fix: - Find the ward config key or env knob that controls git committer identity for warded containers. - Set the deployment default to: - name: `coilyco-ops` - email: `coilyco-ops@coilysiren.me` - Keep per-agent self-name behavior only where it is intentionally author-name display behavior. The bot identity must be the committer/account-linking identity, not an example fallback. - Update `docs/dev-base-git-identity.md` if its current explanation is stale or incomplete. - Add or update tests so a future config change cannot regress to an example identity. Do not assert unrelated KDL content; test the owning identity field or the rendered/loaded config behavior. Validation: - Run `ward doctor`. - Run relevant tests through ward. - Verify a resolved warded launch or equivalent config render no longer contains the example bot identity and resolves the git committer name/email to the `coilyco-ops` bot. Acceptance: - The coilyco ward overlay explicitly configures git committer identity for warded containers. - The example bot identity is not present in the resolved launch identity path. - Commits from warded containers attribute to `coilyco-ops` as committer/account identity.

coilyco-ops referenced this issue

2026-07-13 18:59:46 +00:00

Move ward workflow config out of defaults #501

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-13 21:57:36 +00:00

Configure warded git committer identity #508

coilyco-ops commented

2026-07-13 21:59:43 +00:00

Author

Member

WARDED_WORKFLOW: #508

details

workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because the temporary ward default pending brokered QA). Repair dispatch is active on the same PR after main moved.

The change felt straightforward once the runtime check showed the stale bundle snapshot was the blocker. Confidence is high enough for merge-ready, but the live deployed config still depends on the PR landing and the release path republishing the bundle. Surprise: the current container was still resolving the example-bot defaults until the branch was committed and pushed.

Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/508 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because the temporary ward default pending brokered QA). Repair dispatch is active on the same PR after main moved. The change felt straightforward once the runtime check showed the stale bundle snapshot was the blocker. Confidence is high enough for merge-ready, but the live deployed config still depends on the PR landing and the release path republishing the bundle. Surprise: the current container was still resolving the example-bot defaults until the branch was committed and pushed. Follow-ups: none. </details>

coilyco-ops commented

2026-07-13 22:02:35 +00:00

Author

Member

PR #508 is green but conflicted after #506 merged. Repair request: update branch issue-504 against current main, keep the committer identity change, and drop the stale tests/test_ward_specs_bundle.py edits because #506 deleted that file. Then rerun the repo validation and update the existing PR.

PR #508 is green but conflicted after #506 merged. Repair request: update branch `issue-504` against current `main`, keep the committer identity change, and drop the stale `tests/test_ward_specs_bundle.py` edits because #506 deleted that file. Then rerun the repo validation and update the existing PR.

coilyco-ops closed this issue

2026-07-14 00:53:26 +00:00