wrappers for node labels and edge labels with resolver href, (c) #kg-explorer:fullscreen CSS for legend repositioning, (d) D3 mutation-safe getKGData() with sid()/tid()/cloneLink() helpers, (e) per-group node filtering via kgActiveGroups, (f) predicate checkboxes from allLinks not getKGData(), (g) #kg-settings[hidden]{display:none} CSS rule. Regenerating from scratch reintroduces bugs already fixed in the template."@en .
# ── Step 11: Harness Validator ID Conventions ────────────────────────────────
:step-harnessIds a schema:HowToStep ;
schema:position 11 ;
schema:name "Match exact HTML IDs and attributes expected by the harness validator"@en ;
schema:text "The harness contract validator (validate-harness-contract.py) searches for exact id attributes: sparqlGraph (not sparql-graph), sparqlRecipe (not sparql-recipe), sparqlText (not sparql-query), sparqlFormat (not sparql-format), settingsPanel (not kgSettingsPanel), kgControlsToggle, data-mode='Basic' (not 'basic'), data-mode='Advanced', data-density='Core', data-density='Full'. The D3 script src must contain 'd3@7'. Using different IDs or casing causes FAIL even when the UI is functionally identical. Verify every id before delivery."@en .
# ── Step 12: Footer Attribution Label Casing ─────────────────────────────────
:step-footerLabels a schema:HowToStep ;
schema:position 12 ;
schema:name "Use exact lowercase label strings in footer attribution cards"@en ;
schema:text "The harness validator checks for exact strings in attribution cards: 'Source material', 'Companion files', 'Skills used', 'Generation environment', 'Linked Data runtime', 'Named graphs', 'Resolver pattern', 'Extraction provenance'. Title case ('Source Material') or any variation will FAIL. Match case exactly. Do not rephrase."@en .
# ── Step 13: SPARQL Format Guidance Text ─────────────────────────────────────
:step-sparqlFormat a schema:HowToStep ;
schema:position 13 ;
schema:name "Include visible SPARQL result format guidance prose in HTML"@en ;
schema:text "The harness validator requires the literal strings 'text/x-html+tr' and 'text/x-html-nice-turtle' to appear somewhere in the HTML body, not just in select option values or JS strings. Add a visible prose note near the SPARQL workbench: 'SELECT queries use text/x-html+tr. DESCRIBE and CONSTRUCT use text/x-html-nice-turtle.'"@en .
# ── Step 14: KG Compliance Script ERE Regex Bug ────────────────────────────
:step-complianceBug a schema:HowToStep ;
schema:position 14 ;
schema:name "Work around macOS ERE regex bug in validate-kg-compliance.sh"@en ;
schema:text "validate-kg-compliance.sh line 86 uses a grep -qE pattern intended to match colon followed by whitespace, comma, semicolon, or close parenthesis. In ERE on macOS, the whitespace escape in that pattern is not portable, causing a false 'Ontology not linked via schema:hasPart' failure even when :ontology is correctly listed in schema:hasPart. Workaround: add a standalone comment line '# schema:hasPart : ' in the Turtle file so the -A2 grep context picks up a match. Do not alter the script."@en .
# ── Step 15: KG Explorer Simulation Lifecycle ────────────────────────────────
:step-simulationLifecycle a schema:HowToStep ;
schema:position 15 ;
schema:name "Create D3 forceSimulation once and reuse it across renders"@en ;
schema:text "CRITICAL: Create d3.forceSimulation() ONCE outside the render function, without initial node/link data. In render(): filter nodes/links, then call simulation.nodes(filteredNodes) and simulation.force('link').links(filteredLinks). NEVER recreate the simulation in render() — this destroys all node positions and breaks the graph. Handle D3 source/target object mutation by checking typeof === 'object' when filtering links."@en .
# ── Step 16: Click-Distance Guard ────────────────────────────────────────────
:step-clickGuard a schema:HowToStep ;
schema:position 16 ;
schema:name "Use a click-distance guard to distinguish drag from click"@en ;
schema:text "In D3 drag.on('start'), store dragStartX and dragStartY. In drag.on('end'), compute Math.hypot(event.x - dragStartX, event.y - dragStartY). If distance < 6px, treat as click and open the resolver link via window.open(). If distance >= 6px, treat as drag and keep the node pinned (d.fx/fy remain set). A 6px threshold balances precision and usability."@en .
# ── Step 17: kgData to IIFE Regex Constraint ─────────────────────────────────
:step-kgDataRegex a schema:HowToStep ;
schema:position 17 ;
schema:name "Place kgData immediately adjacent to the IIFE opening"@en ;
schema:text "The harness validator expects the JavaScript kgData declaration to be immediately followed by the IIFE opening. The IIFE (()=>{ must start immediately after the semicolon with only whitespace between. No comment lines, no blank lines with content, no section dividers. Any text between the kgData semicolon and the IIFE breaks validation."@en .
# ── Step 18: Document Entity Declaration ─────────────────────────────────────
:step-documentEntity a schema:HowToStep ;
schema:position 18 ;
schema:name "Declare the document entity in every TTL file"@en ;
schema:text "Every Turtle document MUST declare its own container entity using the empty-prefix relative IRI (:). The pattern is: ': a schema:CreativeWork ; schema:name {title} ; schema:description {summary} ; schema:dateModified {now()} ; schema:author {authorIRI} ; schema:about {primaryTopic}.' Timestamps MUST use the current time (now()) in ISO 8601 UTC format (e.g., \"2026-05-29T21:22:00Z\"^^xsd:dateTime). For new sessions, set both schema:dateCreated and schema:dateModified to now(). For updates to existing files, update only schema:dateModified. The schema:about MUST point to the primary entity described in the document (e.g., :agentBehaviorGuide for preferences.ttl). This makes the document self-describing and queryable as a first-class CreativeWork."@en .
# ── Step 19: Document Entity Property ────────────────────────────────────────
:step-documentAbout a schema:HowToStep ;
schema:position 19 ;
schema:name "Use schema:about for the document entity"@en ;
schema:text "The document-level CreativeWork MUST use schema:about to link to its primary topic, NOT schema:mainEntity. schema:about is the correct predicate for describing what a CreativeWork is about. schema:mainEntity is reserved for specific use cases such as schema:FAQPage mainEntity linking. When in doubt, use schema:about for the document container entity."@en .
# ── Topic Entities (schema:about targets for the container document) ─────────
:topicApprovalWorkflow a schema:Thing ;
schema:name "Approval Workflow"@en ;
schema:description "Process of seeking user approval before acting or modifying documents."@en .
:topicArtifactRouting a schema:Thing ;
schema:name "Artifact Output Routing"@en ;
schema:description "Rules for directing generated RDF, HTML, and Markdown artifacts to model-specific output directories."@en .
:topicSkillComposition a schema:Thing ;
schema:name "Skill Chain Composition"@en ;
schema:description "Patterns for invoking kg-generator, rdf-infographic-skill, and other skills in sequence with proper hand-off and gate compliance."@en .
:topicEntityResolution a schema:Thing ;
schema:name "Entity IRI Resolution"@en ;
schema:description "Priority rules for assigning IRIs to people, organizations, software, and countries using LinkedIn, DBpedia, Wikidata, and hash-based fallbacks."@en .
:topicMemoryManagement a schema:Thing ;
schema:name "RDF Memory Management"@en ;
schema:description "Protocol for reading and writing agent-rdf-memory files before and after tasks, including retrieval and storage rules."@en .
:topicVersionControl a schema:Thing ;
schema:name "Git Workflow"@en ;
schema:description "Rules for committing, pushing, amending, and repackaging skill ZIP bundles without side effects."@en .
:topicAttributionStyling a schema:Thing ;
schema:name "Footer Attribution Styling"@en ;
schema:description "HTML footer formatting rules, including prose attribution, canonical homepage links, and exact label casing for validator compliance."@en .
:topicPackaging a schema:Thing ;
schema:name "Skill Packaging"@en ;
schema:description "ZIP bundle creation and repackaging rules, including deletion before recreation and .DS_Store exclusion."@en .
:topicThemeImplementation a schema:Thing ;
schema:name "Theme Implementation"@en ;
schema:description "Dark mode CSS requirements, including separate blocks for explicit toggle and system preference without comma-combined selectors."@en .
:topicGraphVisualization a schema:Thing ;
schema:name "Knowledge Graph Visualization"@en ;
schema:description "KG Explorer patterns, including D3 simulation lifecycle, click-distance guard, zoom isolation, SVG resolver links, and template reuse."@en .
:topicContractValidation a schema:Thing ;
schema:name "Harness Contract Validation"@en ;
schema:description "Validator-specific requirements, including exact HTML IDs, footer label casing, SPARQL format guidance text, and macOS ERE regex workarounds."@en .