Feedback wanted: needs and wishes for synth #1132

As part of a September 2026 org-wide status review, we are collecting feedback for each PulseEngine repository.

If you use, maintain, or integrate with synth, please share:

• Needs — what is missing or blocking you? Bugs, missing capabilities, documentation gaps, integration friction with the rest of the toolchain.
• Wishes — what would make this tool better? Features, workflow improvements, quality-of-life changes.
• Priorities — if you could pick one thing for the next release, what would it be?

All input feeds into triage and release planning. Comments are welcome from anyone — maintainers, users, and agents alike.

Filed as part of the org-wide review on 2026年09月02日.

Temper hardening — does the org standard fit this repo?

temper applies the org-wide repository hardening. What this repo currently gets from it:

• Branch protection / ruleset (temper-default-branch-protection): signed commits required, no force pushes, no branch deletions, enforce-admins on, strict "branch must be up to date before merge", 0 required approving reviews.
• No required-check floor: the org-wide required status-check list is intentionally empty (a 2026年05月10日 audit found not every repo defines Format/Clippy/Test under those names, and requiring them would leave those repos un-mergeable). Repos with richer CI get extra required contexts per-repo via direct API (e.g. spar's 13-context smithy set).
• Merge policy: merge commits and squash allowed, rebase merges disabled, auto-merge enabled, head branches auto-deleted after merge.
• Bot PR auto-merge: dependabot (and thrum) PRs are squash-auto-merged once checks pass.
• Label sync in merge mode: the 8 standard labels (bug, enhancement, documentation, good first issue, help wanted, question, dependencies, automation) are created/updated; custom labels are left alone.
• Dependabot config generation (weekly), config changes delivered as [temper] Configuration update PRs, plus an AI-review + rivet-oracle pass on PRs.

Please be specific about temper's rules for this repo:

1. Friction — do any of these rules get in your way here (signed commits, strict up-to-date, no rebase merges, dependabot auto-merge, the 0-review requirement)?
2. Required-check floor — should this repo's branch protection require specific status checks? If so, name the exact job names in this repo's CI that should become required contexts.
3. Coverage gaps — anything temper should manage here that it doesn't (CODEOWNERS, starter workflows via pulseengine/.github, org-level Actions policy, secret scanning, release/tag protection, ...)?
4. Labels / dependabot / review bot — wishes on the label set, dependabot cadence or grouping, or the AI + rivet-oracle PR review behavior?