Distillery Knowledge Graph
Feedback capture
Capture a concrete issue while the context is fresh, keep the draft locally in the browser, and copy out a clean markdown or JSON payload for the next ticket, commit note, or handoff. This is intentionally repo-native and static: it standardises reporting without pretending there is a server workflow behind it.
Issue Builder
Use this to draft a structured issue. Query params from the operator surfaces can prefill context, and the current draft is autosaved locally.
<section class="panel">
<h2>Issue Payload</h2>
<p class="hint">Copy either form directly into the next ticket or handoff. The build fingerprint is injected automatically so the report carries concrete repo context.</p>
<div class="codebox">
<button class="copy" id="copyMarkdown" type="button">Copy</button>
<pre id="markdownOut"></pre>
</div>
<div class="codebox">
<button class="copy" id="copyJson" type="button">Copy</button>
<pre id="jsonOut"></pre>
</div>
<div class="status" id="copyStatus"></div>
</section>
Build Fingerprint
The current graph shape and gate status the report will carry with it.
<section class="panel">
<h2>Saved Drafts</h2>
<p class="hint">Draft snapshots are stored locally in this browser only. Use them to capture multiple issues during one pass.</p>
<div class="draft-list" id="drafts"></div>
</section>
Operator Routes
Jump back to the relevant surface once the issue draft is captured.
<section class="panel">
<h2>Source Artifacts</h2>
<p class="hint">Primary files to inspect or link when the report needs stronger evidence.</p>
<div class="artifact-grid" id="artifacts"></div>
</section>