Audit command updates `is_secret` but not `is_verified` – clarification needed

[AnjaneyuluBairi]

Description

While using detect-secrets audit, I noticed that answering Yes/No to the audit prompt:

"Should this string be committed to the repository?"

does not update the is_verified field, but instead adds a new field is_secret: true/false.

Example after audit:

{
  "is_verified": false,
  "is_secret": false
}

Expected / Clarification Needed
Could you please clarify:

1. Whether is_verified is now considered a legacy / unused field
2. Whether the presence of is_secret is the correct way to determine that a finding has been audited
3. Whether documentation should be updated to reflect this newer audit behavior