Phase 5.2-C: Align POPL entry folder structure with external validation runs (GenSpark)

[genspark-ai-developer]

Background

Currently, proofscan popl commands assume a local .popl/popl_entries/ structure.
GenSpark-driven validation runs generate their own output directories containing:

• client execution logs
• pfscan proxy artifacts
• POPL.yml and related files

To support automated 2-layer evidence collection, these folder structures must be aligned or importable without manual intervention.

Scope

Define a canonical directory structure for POPL entries:

• Ensure that:
  • pfscan popl ls / show can operate on GenSpark-produced outputs
  • or GenSpark outputs can be generated directly in POPL-compatible structure
• This alignment is expected to be used by the Validation Client

Acceptance Criteria

• A clear rule exists for where POPL entries live on disk
• GenSpark validation output follows or can be imported into this structure
• pfscan popl commands can list and show entries created via GenSpark runs
• No breaking changes to existing POPL entries

Related

Part of Phase 5.2 - MCP full-spec validation and POPL alignment

See also:

• Phase 5.2-A: Extend Validation Client to cover MCP resources / prompts #28 Phase 5.2-A: Extend Validation Client to cover MCP resources / prompts
• Phase 5.2-B: POPL support for MCP utilities (tasks / progress / cancellation) #29 Phase 5.2-B: POPL support for MCP utilities (tasks / progress / cancellation)