historic_sql_patterns

1# Historic SQL Patterns
2 
3Use this skill when the WorkUnit raw file is a `patterns-input/part-0001.json` style shard from the `historic-sql` adapter. Older staged bundles may still provide root `patterns-input.json`; when that is the WorkUnit raw file, read it the same way.
4 
5## Required Workflow
6 
71. Read the WorkUnit notes first.
82. Find the single pattern input file listed under the WorkUnit `rawFiles` section.
93. Call `read_raw_file` for that exact raw file path.
104. Identify recurring analytical intents that span at least two tables and have repeated usage signal.
115. Emit one `pattern` evidence object per durable cross-table intent by calling `emit_historic_sql_evidence`.
126. Stop after all pattern evidence has been emitted.
13 
14Every join column mentioned in pattern descriptions must be verified via
15entity_details for both sides of the join.
16 
17## Identifier Verification Protocol
18 
19Before writing a wiki page or SL source on any topic:
20 
211. `discover_data({query: "<topic>"})` - see what wikis, SL sources, and raw
22   tables already exist. Prefer updating existing pages over creating new ones.
23 
24Before emitting any `schema.table` or `schema.table.column` into a wiki body,
25SL source, `tables:` frontmatter, `sl_refs`, or `emit_unmapped_fallback`:
26 
272. `entity_details({connectionId, targets: [{display: "<identifier>"}]})` -
28   confirm the identifier resolves; inspect native types, FK/PK, and
29   sampleValues.
303. For literal values from the source, such as status codes or plan tiers,
31…