Replace acceptVPWithoutHolderProof with DCQL require_cryptographic_holder_binding in Verify UI

[mayuradesh]

Title

DataShare flow will break after removing Presentation Definition — migrate to DCQL & update VP Request

---

Description

The current DataShare flow depends on Presentation Definition in the VP Request. Once we remove Presentation Definition, this flow will break unless corresponding changes are made.

To keep the flow intact, Inji Web must migrate to DCQL for querying credentials.

Additionally, the acceptVPWithoutHolderProof flag in VP Request is now redundant and should be removed. DCQL introduces require_cryptographic_holder_binding, which provides a more standardized way to control whether holder proof is required.

---

Problem

• DataShare flow relies on Presentation Definition
• Planned removal of Presentation Definition will break existing flow
• acceptVPWithoutHolderProof is a non-standard flag and overlaps with DCQL functionality

---

Proposed Changes

1. Migrate Inji Web to DCQL

   • Replace Presentation Definition usage with DCQL queries
   • Ensure compatibility with existing DataShare flow

2. Update VP Request structure

   • Remove:
     • presentation_definition
     • acceptVPWithoutHolderProof
   • Use DCQL field:
     • require_cryptographic_holder_binding

3. Wallet behavior alignment

   • Wallet should rely on DCQL to determine:
     • Whether holder binding proof is required
     • Whether VP without proof is acceptable

---

Impact

• Prevents DataShare flow from breaking post-removal
• Aligns implementation with DCQL standard
• Simplifies VP Request by removing legacy/custom flags

---

Acceptance Criteria

• Inji Web supports DCQL queries for DataShare flow
• VP Request no longer includes presentation_definition
• acceptVPWithoutHolderProof is removed
• Wallet correctly interprets require_cryptographic_holder_binding
• DataShare flow works end-to-end using DCQL

---

Notes

• This is a breaking change if not coordinated properly
• Migration should be synchronized between backend, Inji Web, and wallet

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Support require_cryptographic_holder_binding in DCQL during VP submission for LDP_VC #1965

🔗 Related PRs

#1985 - [INJIVER-1972] fix:incorrect status and number of credentials shared [merged]
#1992 - added fix for #1977 [merged]
#2018 - Injiver 1768 remove vpRequest test [merged]
#2020 - #1768 DCQL support auth request changes in Verify UI [merged]
#2027 - #1957 VP Result Processing & Validation (DCQL + Legacy Support) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!