historic_sql_table_digest

1# Historic SQL Table Digest
2 
3Use this skill when the WorkUnit raw file is one `tables/<schema>.<name>.json` file from the `historic-sql` adapter.
4 
5## Required Workflow
6 
71. Read the WorkUnit notes first.
82. Call `read_raw_file` for the single `tables/<schema>.<name>.json` raw file.
93. Read `manifest.json` only if the table JSON omits the dialect or the WorkUnit notes are unclear.
104. Produce one concise usage narrative for this table from the staged table JSON.
115. Call `emit_historic_sql_evidence` exactly once with `kind: "table_usage"`.
126. Stop after the evidence tool succeeds.
13 
14## Identifier Verification Protocol
15 
16Before writing a wiki page or SL source on any topic:
17 
181. `discover_data({query: "<topic>"})` - see what wikis, SL sources, and raw
19   tables already exist. Prefer updating existing pages over creating new ones.
20 
21Before emitting any `schema.table` or `schema.table.column` into a wiki body,
22SL source, `tables:` frontmatter, `sl_refs`, or `emit_unmapped_fallback`:
23 
242. `entity_details({connectionId, targets: [{display: "<identifier>"}]})` -
25   confirm the identifier resolves; inspect native types, FK/PK, and
26   sampleValues.
273. For literal values from the source, such as status codes or plan tiers,
28   check whether they appear in `entity_details` sampleValues for the relevant
29   column. If sampleValues is short or the sample may have missed real values,
30   run a `sql_execution` probe with the same warehouse connection id:
31…