Support configurable template formats for Oz responses

[captainsafia]

Once the pull requested associated with #338 is in, we should add support for templating the strings that are used in Oz workflow comments. We can store these configurations as multi-line strings in the config file that we are authoring as a result of the linked work.

[oz-for-oss]

@captainsafia

I've finished triaging this issue. A maintainer will verify the details shortly. You can view the triage session on Warp.

Maintainer details

I concluded that this is a workflow enhancement request to make Oz-authored comment text configurable instead of hardcoded across the workflow scripts..

Triage summary

This looks like a follow-on workflow enhancement rather than a bug report.

What I found

• Current Oz-authored workflow comment text is still hardcoded in shared helpers and workflow-specific scripts.
• .github/scripts/oz_workflows/helpers.py defines many stock progress, review, and triage comment strings.
• .github/scripts/triage_new_issues.py and .github/scripts/comment_on_unready_assigned_issue.py also assemble user-facing comment text directly.
• .github/issue-triage/config.json currently exposes label taxonomy only, so there is not yet a checked-in config surface for response templates.

Likely affected files

• .github/scripts/oz_workflows/helpers.py
• .github/scripts/triage_new_issues.py
• .github/scripts/comment_on_unready_assigned_issue.py
• .github/issue-triage/config.json

Triage assessment

• Treat this as a post-Remove Warp-specific hardcoded values from self-improvement scripts for OSS compatibility #338 enhancement to add a repo-level template/config mechanism for Oz-authored workflow comments.
• No reporter follow-up is needed for initial triage; the implementation work should define which comment surfaces become configurable and what template variables are supported.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[captainsafia]

@oz-agent Let's work on a spec for this and ensure that we are building on top of the config format for capturing what the templated string should be.

[oz-for-oss]

@captainsafia

I'm starting work on product and tech specs for this issue.

You can view the conversation on Warp.

I created a new spec PR for this issue.

Preview generated specs:

• Product spec: specs/GH347/product.md
• Tech spec: specs/GH347/tech.md

Next steps:

• Review the spec PR and confirm that the proposed approach looks right.
• Request or make any needed spec updates before moving on to implementation.

Powered by Oz

[oz-for-oss]

@captainsafia

I'm implementing this issue on top of the approved spec PR's branch.

You can view the conversation on Warp.

Powered by Oz