Skip to content

Review and action non-Claude provider parity audit report #672

@julianknutsen

Description

@julianknutsen

Problem

We now have a report for the docs/non-Claude provider parity audit: w-7ed35a727f.

The earlier tracking issue, #350, was for running the audit and producing a maintainer-useful punch list. This follow-up issue is to review the actual report output, confirm which findings are still real on current main, and convert the actionable items into concrete implementation work.

Context

Related prior tracker:

Relevant repo context:

  • engdocs/archive/analysis/gastown-upstream-audit.md
  • Section 35 currently calls out two non-Claude parity themes that need confirmation/actioning:
    • hook/runtime parity for Codex, Copilot, and other non-Claude providers
    • queued/deferred nudge delivery parity for non-Claude providers

Scope

  • review report w-7ed35a727f
  • compare each finding against current Gas City behavior on main
  • separate stale/already-fixed findings from real remaining gaps
  • turn the real gaps into concrete follow-up issues or patches
  • update the audit/report status so maintainers can see what remains open

Acceptance Criteria

  • each finding in w-7ed35a727f is classified as one of:
    • already fixed
    • stale / no longer applicable
    • still actionable
  • actionable findings are linked to discrete follow-up issues or PRs
  • any confirmed parity gaps cite the relevant code/doc locations
  • the resulting tracker state is specific enough that maintainers can execute the remaining work without re-running the audit from scratch

Notes

This issue is intentionally separate from #350:

wasteland:
  type: chore
  priority: 2
  effort: medium
  report: w-7ed35a727f

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/choreInternal improvement (refactor, tests, CI, tooling)priority/p2Medium — real problem, workaround existswastelandTracked by Wasteland sync

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions