Files
vardkey/static/health-check.html
T

147 lines
8.9 KiB
HTML

<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="theme-color" content="#f4f6f2">
<title>Annual health check — VardKey</title>
<link rel="stylesheet" href="/styles.css">
<link rel="manifest" href="/manifest.webmanifest">
<script src="/session.js" defer></script>
<script src="/health-check.js" defer></script>
</head>
<body>
<header class="topbar">
<a class="brand" href="/" aria-label="VardKey dashboard">
<span class="brand-mark" aria-hidden="true">V</span>
<span>VardKey</span>
</a>
<a class="back-link" href="/">Back to dashboard</a>
</header>
<main class="page-shell form-shell">
<div class="page-heading form-heading">
<div>
<p class="eyebrow">Annual security check</p>
<h1>Health check</h1>
<p class="intro">Record what you checked. VardKey does not test devices or backups itself.</p>
</div>
</div>
<div class="privacy-notice" role="note">
Never enter seed phrases, private keys, PINs, passwords, wallet secrets, or contact details.
</div>
<form id="health-check-form">
<section class="form-section" aria-labelledby="schedule-title">
<div class="form-section-heading">
<p class="eyebrow">01 / Schedule</p>
<h2 id="schedule-title">Check date</h2>
</div>
<div class="field-grid">
<label class="field"><span>Check date</span><input id="checked-at" name="checked_at" type="date" required></label>
</div>
<p class="field-help" id="next-check-preview">Next check due is calculated automatically as one calendar year after the check date.</p>
</section>
<section class="form-section" aria-labelledby="key-checks-title">
<div class="form-section-heading">
<p class="eyebrow">02 / Key</p>
<h2 id="key-checks-title">Key check</h2>
</div>
<!-- A key with an open alert cannot get a new check until the alert is
closed, and the note names the alert, the action that closes it, and
the keys that are free (section 26.1). -->
<div class="warning-note" id="blocked-keys-note" role="note" hidden>
<p><strong>One or more keys have an open alert.</strong> A key with an open alert cannot get a new check until the alert is closed, because the alert is closed by the user and not by a newer check.</p>
<ul id="blocked-keys-list"></ul>
<p><a class="back-link" href="/">Open the dashboard to close the alerts</a></p>
</div>
<label class="field"><span>Key being checked</span><select id="key-select" name="key_id" required><option value="">Select a key</option></select></label>
<p class="field-help">One submission records one key. The other keys keep their own next check date.</p>
<p class="field-help">A blocked key is marked in the list and cannot be selected. The other keys can still be checked.</p>
<p class="field-help">The recorded address path is compared with the path stored for the key, and the result is recorded automatically.</p>
<div id="key-check" class="form-stack"><p class="empty-state">Loading key profiles…</p></div>
<!-- The warning appears when the recorded address path does not match the
path stored for the key (section 25.1). -->
<div class="warning-note" id="address-path-warning" role="alert" hidden>
<p>The address path does not match the one stored for this key. Check it against your BSMS and try again, or confirm that you want to record this check anyway.</p>
<p class="field-help">A check recorded anyway keeps the address path, the key note, the contact confirmation, and the overall comment. The hardware, the software, and the security results cannot be recorded, and the check raises a critical alert.</p>
<label class="field checkbox-field"><input id="address-path-confirmed" type="checkbox"><span>Record this check anyway, as a key that could not be checked</span></label>
</div>
</section>
<section class="form-section" id="software-section" aria-labelledby="software-title">
<div class="form-section-heading">
<p class="eyebrow">03 / Compatibility</p>
<h2 id="software-title">Software compatibility</h2>
</div>
<!-- The software choices are built from the settings and the configured
cloud keys (section 25.4). A cloud key hides this grid, because its
software and its compatibility are derived. -->
<div class="field-grid" id="software-grid">
<label class="field"><span>Wallet software</span><select id="wallet-software" name="wallet_software" required><option value="">Select software</option></select></label>
<label class="field"><span>Compatibility status</span><select id="software-compatibility" name="software_compatibility_status" required><option value="">Select status</option><option value="OK">OK</option><option value="PROBLEM">Problem</option></select></label>
</div>
<!-- The version belongs to every key, including a cloud key, so it stays
visible while the grid above is hidden (section 25.5). -->
<div class="field-grid">
<label class="field"><span>Software version</span><input id="software-version" name="software_version" type="text" maxlength="100" autocomplete="off"></label>
</div>
<p class="field-help" id="software-help">Record the version of the software you selected for this key.</p>
<label class="field"><span>Compatibility notes</span><textarea name="software_comments" rows="3" maxlength="2000"></textarea></label>
</section>
<section class="form-section" aria-labelledby="security-title">
<div class="form-section-heading">
<p class="eyebrow">04 / External research</p>
<h2 id="security-title">Security status</h2>
</div>
<p class="field-help">Enter results from your external research; the app does not contact AI or product providers.</p>
<div id="security-checks" class="form-stack"><p class="empty-state">Select a key to see the providers to check.</p></div>
</section>
<section class="form-section" aria-labelledby="contact-title">
<div class="form-section-heading">
<p class="eyebrow">05 / Contact confirmation</p>
<h2 id="contact-title">Contact information</h2>
</div>
<!-- The confirmation is required, also when the key was not available,
because the question is still asked (section 24.1). -->
<label class="field"><span>Have you confirmed that this key holder's contact details are current?</span><select id="contact-info-verified" name="contact_info_verified" required><option value="">Select status</option><option value="Confirmed current">Confirmed current</option><option value="Needs external update">Needs external update</option></select></label>
<p class="field-help">Only the confirmation for the selected key is recorded in the saved check. Do not enter names, email addresses, or phone numbers.</p>
<p class="field-help" id="contact-reminder" hidden>Contact details must be updated in your external documentation.</p>
</section>
<section class="form-section" aria-labelledby="comments-title">
<div class="form-section-heading">
<p class="eyebrow">06 / Notes</p>
<h2 id="comments-title">Overall comments</h2>
</div>
<label class="field"><span>Observations and follow-up notes</span><textarea name="comments" rows="4" maxlength="4000"></textarea></label>
</section>
<div class="form-actions">
<button class="primary-button active-button" type="submit">Review check</button>
<a class="secondary-button" href="/">Cancel</a>
</div>
</form>
<section id="review-panel" class="form-section review-panel" aria-labelledby="review-title" hidden>
<div class="form-section-heading">
<p class="eyebrow">Review</p>
<h2 id="review-title">Check summary</h2>
</div>
<div id="review-summary" aria-live="polite"></div>
<p class="workflow-note">No data from this form has been stored yet. Press <strong>Save health check</strong> to store this check.</p>
<p class="workflow-note" id="save-status" role="status"></p>
<div class="form-actions">
<button class="primary-button active-button" id="save-check" type="button" disabled>Save health check</button>
<a class="secondary-button" href="/">Cancel</a>
</div>
</section>
</main>
<footer class="footer"><span>VardKey</span><span>Your data stays local.</span></footer>
</body>
</html>