Skip to content

[deep-report] Add explicit converter between HostedWebPolicy and AWFHostedWebPolicy #63436

Closed as not planned

Description

@github-actions

Description: pkg/workflow/engine.go:209 (HostedWebPolicy, frontmatter-facing) and pkg/workflow/awf_config.go:225 (AWFHostedWebPolicy, AWF-runtime-facing) share the same 4 conceptual fields (Enabled, Allowed/AllowedDomains, Blocked/BlockedDomains, MaxUses) under different naming conventions, referenced 78 times across 12 files. No explicit converter function currently exists between them, unlike the codebase's established Definition -> Runtime pattern (e.g. EngineCapabilitiesDefinition.ToRuntimeCapabilities()).

Expected Impact: Prevents silent field-add drift in the recently-shipped hosted-web-policy feature (PR #63212) — a future field added to one struct could silently fail to propagate to the other with no compiler error.

Suggested Agent: New Agent (Go refactoring)

Estimated Effort: Quick (~1h)

Data Source: DeepReport analysis of Typist Go Type Consistency Analysis discussion #63418 (2026-09-25), Cluster 3. Dedup-checked via search — no matching open issue found.

Generated by 🔬 Deep Report · claude · agent · 140 AIC · ⌖ 9.64 AIC · ⊞ 13K · ◷

  • expires on Sep 27, 2026, 4:44 AM UTC-08:00

Activity

  1. github-actions commented on Sep 27, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-09-27T12:44:40.248Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions