KB ARTICLE BUILDER

The original file contained <header class="topbar"> with a .tb-brand div containing the KTC logo and all associated CSS blocks (.topbar, .tb-brand, .tb-logo, .tb-name, .tb-right, .tb-btn, .tb-tag). These were removed. The page now uses the IVR-pattern topbar with the layer-badge and Orbitron h1, inheriting nav from the parent shell.

The original used JetBrains Mono / Exo 2 / Inter font stack, a #020406 background, and CSS tokens like --surface, --bdr, --txt2. All replaced with IVR ground-truth tokens: Orbitron / Share Tech Mono / Rajdhani, #0a0a0f bg, and the exact --panel / --border / --text / --cyan etc. variable set. Grid and scanline overlays match the IVR console exactly.

Original code always executed node${currentStep}.classList.add('done') regardless of direction. Navigating backward (e.g. step 3 → step 1) marked node3 as "done" even though the user was going back, leaving incorrect green "completed" markers on nodes the user went back past.

Fix: wrapped the done-add in a forward-only guard. When going backward, all nodes from the destination index onward have their "done" class removed.

Four pill groups captured state that was only used in buildPreview() but silently dropped from both buildPlainText() and submitArticle(): product/platform, OS scope, affected users, and time estimate. All four are now included in the plain-text export (added as labelled lines after Tags) and in a new "Product / OS / Affected" summary card plus "Est. Time" summary card. A helper function getPillVals(id) is used consistently across all three output paths.

The reset function used querySelectorAll('.toggle-opt, .prio-card, .pill') which missed .callout-opt buttons. After a reset, any previously selected callout type (Note / Tip / Warning / Critical) remained visually selected. Fixed by adding .callout-opt to the selector.

The file is a sub-page of the MSP AI Platform parent shell. The original file had no <script src="../nav.js" defer></script> tag. Added without touching any other functionality. Will silently 404 if opened standalone — expected behavior.

The original had no loadDashboard(), startAutoRefresh(30000), or refreshAll() — inconsistent with the rest of the console suite. All three added. isLive flag defaults false. Commented-out real fetch() call placed in submitArticle() for KB persistence. Demo banner added matching the IVR console pattern. Status dot shows DEMO MODE (yellow) / KB API ONLINE (green).

Articles generate a local KB ID (KB-YYYYMMDD-XXXX) using Date + Math.random(). IDs are not globally unique across sessions and are not stored anywhere. Articles exist only in memory until exported or copied. Wire POST /kb/articles in submitArticle() when a KB backend is available.

There is no native KB article creation endpoint in the ConnectWise Manage REST API. CW Manage's closest option is POST /service/tickets/{id}/notes — attaching the article text as an internal note on a ticket. IT Glue has a Documents API (POST /documents) but requires an API key and auth headers managed by the proxy. Both require proxy activation.

ConnectWise Manage has no CSAT satisfaction score in the public REST API. Not applicable to this tool type but documented for suite consistency. Use SmileBack or Nicereply integrations for CSAT data.

navigator.clipboard.writeText() is restricted to secure contexts (HTTPS or localhost). On plain HTTP the call will be rejected. The export (.txt download) path works regardless of protocol.

Opening tl-kb-builder.html standalone will produce a 404 on ../nav.js. This is expected — the nav is injected by the parent shell. The wizard functionality works fully without the nav.

There is no localStorage draft save. Closing or refreshing the browser tab discards all wizard progress. A draft auto-save could be added by serialising state to localStorage on each step transition — not yet implemented.