[DD] Initial FE implementation

[Dr-Pongo]

Issue Description

Create an initial version of the Digital Dispute with all required pages. We don't have a URL yet, or a fully functioning vets-api endpoint, so this can live on a remote branch until we're ready to merge.

• Backend ticket for prefill stuffs:
  DD Prefill data #98021

Definitions:

• POST: debts_api/v0/digital_disputes
• App name in vets-website: src/applications/dispute-debt
• Root URL: <env>/manage-va-debt/dispute-debt/

Links:

• Figma page layouts
• Application generator
• CAIA Mural with url definitions and other helpful stuffs
• URL Guidance
• VA Forms Library

Tasks

• Implement first version of the form for vets-website
• Include necessary unit tests
• Once initial draft is up, review with Design

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required

Acceptance Criteria

• Initial version of Digital dispute is created
• Initial version has been reviewed with design

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the "Then" statement in the description

Test procedures:
If additional testing steps or credentials to perform testing are needed list them here

Ticket Creation - Definition of Ready

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Attach to an Epic
• Estimate Points

[Dr-Pongo]

Rolling over because it's a big effort that got started late in the sprint!

[Dr-Pongo]

Feature flag is nearly ready to be merged

• [DD] Create Digital Dispute feature toggle #96916

Initial PR for Digital Dispute in vets-website

• [DD] Dispute Debt initial vets-website#33151

Initial PR for DIgital DIspute in vets-api

• [DD] Initial prefill for digital dispute vets-api#19545
  Todo list after initial PR is merged

[Dr-Pongo]

Opened PR for vets-json-schema which is the true first step in merging on vet-website and vets-api. Waiting on feedback on PRs before proceeding and discussing structure and future steps/work the schema in general and how it aligns with the white list for api.

Edit:
Wanted to add some documentation context. We are following the platform documentation on Moving a Form to Production.

I think to call this effort done we need platform approval and to merge the following (in order)

1. Add schema for Dispute Debt vets-json-schema#961
2. [DD] Initial prefill for digital dispute vets-api#19545
3. [DD] Dispute Debt initial vets-website#33151

[Dr-Pongo]

After some changes suggested by the team, I opened a support ticket to get a platform review!
https://dsva.slack.com/archives/CBU0KDSB1/p1733156945943879

Edit: reread the docs, and requesting platform approval is 3 days after team reviews 😬 So I will re-request Wednesday
Edit 2EB: We have approval on the first step!

[Dr-Pongo]

Need to address some of the CI issues for the vets-website to get it to merge (close PR, rebase, open new PR?)
. We can likely close the ticket after that, although the BE PR may block it as well.

[Dr-Pongo]

So fresh so clean new FE PR (rebased and made new PR to hopefully pickup the schema changes

• [DD] Dispute Debt initial vets-website#33332

[Dr-Pongo]

Rolled into 140 while troubleshooting errors and managing other high priority tasks

[Dr-Pongo]

Still troubleshooting CI/CD issues

[Dr-Pongo]

Opened support ticket looking for assistance with CI issues:
https://dsva.slack.com/archives/CBU0KDSB1/p1733761378310059

[Dr-Pongo]

Still coordinating with Platform to find a resolution. A few fixes have been made in the vets-json-schema to include a necessary property type, but still seeing vets-website CI failures with:

Error: Cannot find module 'jsdom'

Updating as blocked after a test branch confirmed wonky CI issues unrelated to dispute debt specific changes

• test branch
  Updating vets-json-schema dependency to latest (24.7.0) vets-website#33495

[Dr-Pongo]

Supporting PRs got merged to fix some platform level issues, waiting for platform approval. If we don't get it by end of sprint, I'll likely close the PR, and leave notes in FE documentation on the branch that contains the skeleton for Dispute Debt so we can hit the ground running in the new contract

[Dr-Pongo]

Closing out at end of sprint/contract. The initial app implementation is in the remote branch dd/97002/new-app-initial, and we'll still need a content-build PR to update the registry with the new URL.