{% extends "base.html" %}
{% block title %}Server releases{% endblock %}
{% block page_id %}server-management{% endblock %}
{% block head %}<style>
.sm-grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,320px),1fr));gap:16px}.sm-form label{display:block;margin:12px 0 4px}.sm-form input,.sm-form select,.sm-form textarea{width:100%;box-sizing:border-box}.sm-live{border-left:5px solid #f0a44b}.sm-test{border-left:5px solid #5ac8fa}.sm-card pre{white-space:pre-wrap;overflow-wrap:anywhere}.sm-card{min-width:0}.sm-state{font-weight:700}.sm-form summary{cursor:pointer}.sm-grid>.a-card{margin:0}
</style>{% endblock %}
{% block content %}
<div class="a-page-head"><h1>Server releases</h1><p class="a-sub">See the artifact with test evidence beside the version your own server reports.</p></div>
<p class="a-hint">Start by <a href="{{ aida_rel('fleet') }}">adding your server in Fleet</a> with your saved SSH connection. Each destination belongs to an application and an explicit TEST or LIVE environment.</p>
<p id="sm-status" role="status" aria-live="polite">Loading saved destinations...</p>
<div class="a-toolbar"><button class="a-btn" id="sm-refresh" type="button">Refresh saved evidence</button><a class="a-btn" href="{{ aida_rel('deploy-lite') }}">File deployment tools</a></div>
<div id="sm-destinations" class="sm-grid"></div>
<div class="sm-grid" style="margin-top:20px">
<section class="a-card sm-form"><h2 id="sm-form-title">Add your destination</h2><form id="sm-destination-form">
<label for="sm-name">Destination name</label><input class="a-input" id="sm-name" maxlength="160" required>
<label for="sm-device">Saved Fleet device</label><select class="a-input" id="sm-device" required></select>
<label for="sm-app">Application name</label><input class="a-input" id="sm-app" maxlength="160" required>
<label for="sm-environment">Environment</label><select class="a-input" id="sm-environment" required><option value="">Choose TEST or LIVE</option><option value="test">TEST</option><option value="live">LIVE</option></select>
<label for="sm-path">Application runtime JSON path on this server</label><input class="a-input" id="sm-path" required autocomplete="off">
<label for="sm-age">Maximum heartbeat age (seconds)</label><input class="a-input" id="sm-age" type="number" min="10" max="900" value="120" required>
<p class="a-hint">Uses the saved device credentials and known SSH host key. Test and live require distinct device/path destinations.</p><button class="a-btn" type="submit">Save destination</button></form></section>
<section class="a-card sm-form"><h2>Artifact and test evidence</h2><p>Import your build producer's artifact identity and its matching JUnit receipt. Imported test results are producer reports; AidaIDE has not independently rerun or attested them.</p>
<label for="sm-artifact">Artifact identity JSON</label><textarea class="a-input" id="sm-artifact" rows="7" spellcheck="false"></textarea><button class="a-btn" id="sm-add-artifact" type="button">Record artifact</button>
<label for="sm-receipt">JUnit receipt JSON</label><textarea class="a-input" id="sm-receipt" rows="7" spellcheck="false"></textarea><button class="a-btn" id="sm-add-receipt" type="button">Import matching receipt</button>
<details><summary>Integration contract</summary><p>Artifact: version, sha256 (built bytes), full commit, dirty (boolean), source_sha256 (exact build source snapshot). Receipt: artifact_id (shown below), artifact (the same complete identity), suite, producer, finished_at (UTC Unix seconds), junit_xml. Empty, skipped, failed or mismatched reports do not become passing evidence.</p><p>Your running application must atomically refresh its JSON heartbeat: schema=1, application, environment, artifact, deployment_id (from Prepare arrival check), instance_id (unique per process start), started_at, reported_at (UTC Unix seconds), health (healthy, unhealthy or unknown). A fresh matching process must report within 10 minutes. Keep clocks synchronized.</p></details>
<div id="sm-artifacts"></div></section></div>
<section class="a-card sm-form" id="smw-root" style="margin-top:20px"><h2>Producer evidence and deployment review</h2>
<p>Use files from your own build/test producer. AidaIDE checks their bytes before importing evidence. The producer remains responsible for the build and test claims.</p>
<div class="sm-grid"><div><h3>Import local producer bundle</h3>
<label for="smw-artifact">Built artifact file on this PC</label><input class="a-input" id="smw-artifact" autocomplete="off">
<label for="smw-manifest">Producer bundle JSON file on this PC</label><input class="a-input" id="smw-manifest" autocomplete="off">
<label for="smw-report">Matching JUnit XML file on this PC</label><input class="a-input" id="smw-report" autocomplete="off">
<div class="a-toolbar"><button class="a-btn" id="smw-review" type="button">Review producer files</button><button class="a-btn" id="smw-import" type="button" data-sm-disabled="yes" disabled>Import reviewed evidence</button><button class="a-btn" id="smw-clear" type="button">Discard local reviews</button></div>
<p class="a-hint">The build producer can create the manifest with tools/create_server_release_bundle.py. Import checks actual artifact/report bytes and the source-manifest digest, without rerunning or independently attesting tests.</p>
<pre id="smw-evidence" style="white-space:pre-wrap;overflow-wrap:anywhere"></pre></div>
<div><h3>Review one destination</h3>
<label for="smw-destination">Explicit TEST or LIVE destination</label><select class="a-input" id="smw-destination"></select>
<label for="smw-release">Intended artifact</label><select class="a-input" id="smw-release"></select>
<label for="smw-file">Local artifact file for deployment planning</label><input class="a-input" id="smw-file" autocomplete="off">
<label for="smw-remote">Remote release directory to review</label><input class="a-input" id="smw-remote" autocomplete="off">
<div class="a-toolbar"><button class="a-btn" id="smw-plan" type="button">Preview deployment</button><button class="a-btn" type="button" data-sm-disabled="yes" disabled>Deploy (not configured)</button></div>
<p class="a-hint">Local preview only. No SSH connection, transfer, remote preflight or service action is performed. Deployment and rollback require a verified activation and backup adapter. Configure systemd logs and restart below.</p>
<div class="a-toolbar"><button class="a-btn" id="smw-logs" type="button">Preview logs setup</button><button class="a-btn" id="smw-restart" type="button">Preview restart setup</button><button class="a-btn" id="smw-rollback" type="button">Preview rollback setup</button></div>
<pre id="smw-plan-result" style="white-space:pre-wrap;overflow-wrap:anywhere"></pre></div></div>
<p id="smw-status" role="status" aria-live="polite">Choose local files or a customer destination to review.</p></section>
<section class="a-card sm-form" id="sc-root" style="margin-top:20px"><h2>Configured service controls</h2>
<p>Uses the explicit TEST or LIVE destination selected above and its saved SSH account. Configure your own canonical systemd service; no service or operation is enabled automatically.</p>
<p id="sc-capabilities" role="status">Choose a destination above.</p>
<div class="sm-grid"><div>
<label for="sc-unit">Your canonical service unit</label><input class="a-input" id="sc-unit" autocomplete="off">
<label for="sc-scope">Service manager scope</label><select class="a-input" id="sc-scope"><option value="user">User service manager</option><option value="system">System service manager</option></select>
<label><input id="sc-logs-permission" type="checkbox" style="width:auto"> Allow bounded journal reads</label>
<label><input id="sc-restart-permission" type="checkbox" style="width:auto"> Allow reviewed restarts</label>
<label for="sc-lines">Maximum captured journal lines</label><input class="a-input" id="sc-lines" type="number" min="1" max="200" value="50">
<div class="a-toolbar"><button class="a-btn" id="sc-save" type="button">Review adapter configuration</button><button class="a-btn" id="sc-remove" type="button">Remove adapter</button><button class="a-btn" id="sc-reload" type="button">Reload adapter fields</button></div>
<p class="a-hint">System scope uses the existing account's permissions. AidaIDE does not change SSH trust, sudo rules, journal access or service configuration. Saving replaces this destination's arrival evidence.</p>
</div><div>
<div class="a-toolbar"><button class="a-btn" id="sc-read" type="button" data-sm-disabled="yes" disabled>Read service logs</button><button class="a-btn" id="sc-review" type="button" data-sm-disabled="yes" disabled>Review restart</button><button class="a-btn a-btn--danger" id="sc-restart" type="button" data-sm-disabled="yes" disabled>Confirm reviewed restart</button></div>
<div class="a-toolbar"><button class="a-btn" id="sc-cancel" type="button" data-sm-interrupt="yes" data-sm-disabled="yes" disabled>Stop owned request</button><button class="a-btn" id="sc-close" type="button" data-sm-interrupt="yes">Close owned controls</button></div>
<p id="sc-status" role="status" aria-live="polite">No service operation has run.</p>
<pre id="sc-output" style="white-space:pre-wrap;overflow-wrap:anywhere"></pre>
<details><summary>Checked service receipt</summary><pre id="sc-receipt" style="white-space:pre-wrap;overflow-wrap:anywhere"></pre></details>
</div></div>
<p class="a-hint">Restart success requires an active fresh service invocation. It does not verify application version or health; observe runtime again. Stopping a request closes its owned helpers, but a restart may already have taken effect.</p></section>
<p class="a-hint">Prepare arrival check records an expectation only. Your own deployment integration must launch the artifact and supply the rollout ID. Observe performs a bounded SFTP read. Arrival and health are application-reported, so the runtime heartbeat must come from the running process. An uploaded build manifest or successful CI run alone cannot prove arrival.</p>
{% endblock %}
{% block scripts %}<script src="{{ aida_rel('static/js/server_management.js') }}"></script><script src="{{ aida_rel('static/js/server_release_workflows.js') }}"></script><script src="{{ aida_rel('static/js/server_controls.js') }}"></script>{% endblock %}