substrate: laptop-only source integration (../scratch = Ace pkg mgr / ../SQLSharp = pre-DBSP streaming) HIGH PRIORITY backlog

[AceHack]

Summary

Aaron 2026-04-27 input: every `../scratch` and `../SQLSharp` reference in the repo points at directories that exist ONLY on Aaron's laptop. Future maintainers / agents / contributors cannot access them. HIGH PRIORITY backlog item to integrate the features OR write designs detailed enough we no longer need the references.

Critical clarification (Aaron's third message):

• `../scratch` = the SEED of the future Ace package manager (Aaron's declarative package management product)
• `../SQLSharp` = pre-DBSP event-stream-processing with LINQ/SQL, Zeta's progenitor before he knew about DBSP — features potentially subsumed by Zeta's DBSP-rigorous form

Goal: NOT literal copy-paste. Self-contained understanding floor — repo must contain enough that a future maintainer needs nothing beyond it.

Per-reference triage admits three outcomes:

1. Ship the feature in-repo (small, mature, planned-use)
2. Document the design in-repo with enough detail to rebuild without external reference
3. Delete decorative references (no information loss)

Refined per-directory triage logic:

• For `../scratch` (Ace pkg mgr): toolchain pin → absorb into canonical location; package-manager design decision → design doc; decorative → delete.
• For `../SQLSharp` (pre-DBSP streaming): feature already in Zeta DBSP form → document lineage + delete; outside DBSP scope but needed → design doc; opportunity for future Zeta graduation → BACKLOG row capturing Zeta-canonical reimagining; decorative → delete.

Scope (2026-04-27 grep)

• 22 files reference `../scratch`, 14 reference `../SQLSharp`; 36 unique files, 125 grep hits
• Three feature clusters: (1) toolchain/setup, (2) CI/repo-automation, (3) research/design hints

Done condition

• `git grep -- '../scratch'` returns zero matches
• `git grep -- '../SQLSharp'` returns zero matches
• Every previously-referenced feature is either shipped or design-documented in-repo

Sequencing

This PR is the SUBSTRATE-LANDING for the work, not the work itself. The actual integration is L (3+ days) effort, sequenced AFTER PR #26 sync lands per Aaron's earlier "finish the sync first" framing.

Composes with

• Otto-275 (log-but-don't-implement; default to design when uncertain)
• Otto-323 / Otto-346 (these are NOT external deps — in-repo or eliminate)
• Otto-340 (substrate IS identity; repo must contain the substrate)
• PR sync: AceHack ∪ LFG full reconciliation via per-file content-preserving merge (task #302) #26 (Python pin update proved the pattern)
• PR substrate: install-script language strategy (pre-install bash+PowerShell / post-install TypeScript / Python for AI-ML) #40 (install-script language strategy established the principle)
• linq-expert / sql-expert / sql-engine-expert skills (already track LINQ/SQL streaming class, the SQLSharp lineage)

Test plan

• markdownlint passes on the new memory file
• memory-index-integrity workflow passes (paired MEMORY.md entry)
• No code change — substrate-only PR

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Pull request overview

Adds a new substrate “project” memory entry to track elimination of out-of-tree, laptop-only references to ../scratch (Ace package-manager seed) and ../SQLSharp (pre-DBSP LINQ/SQL streaming prototype), plus an index entry so it’s discoverable from memory/MEMORY.md.

Changes:

• Adds memory/project_laptop_only_source_integration_scratch_sqlsharp_features_or_designs_high_priority_2026_04_27.md documenting the problem framing, triage tactics (ship/design/delete), and proposed “done” criteria.
• Adds a new top-level index bullet in memory/MEMORY.md pointing at the new project memory entry.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
memory/project_laptop_only_source_integration_scratch_sqlsharp_features_or_designs_high_priority_2026_04_27.md	New project memory doc capturing scope + integration/triage plan for removing laptop-only references.
memory/MEMORY.md	Adds an index entry linking to the new project memory doc.

[Copilot]

The frontmatter description hard-codes counts ("22 files" / "14 files" / "125 total grep hits") that don’t match the current repo state (this PR also introduces new ../scratch / ../SQLSharp mentions in memory/). To avoid drift, either recalculate the numbers from a fresh git grep on the post-PR tree (and keep the audit command/output somewhere durable), or rephrase this as approximate scope without exact counts.

Suggested change

description: Aaron 2026-04-27 input — repo currently has 22 files with `../scratch` references and 14 files with `../SQLSharp` references (125 total grep hits) pointing at out-of-tree directories that exist ONLY on Aaron's laptop; future maintainers / agents / contributors can't access them; HIGH PRIORITY backlog item to fully integrate the features OR write detailed-enough designs that we no longer need the out-of-tree references for understanding; KEY CLARIFICATION (Aaron 2026-04-27 second message) — "this is not a copy past, we just want to have either all their features or a design for any of the features we don't have that's detailed enough we no longer need ../scratch or ../SQLSharp reference for understanding"; goal is self-contained understanding + repo independence, NOT literal source copy.

description: Aaron 2026-04-27 input — repo currently contains multiple `../scratch` and `../SQLSharp` references pointing at out-of-tree directories that exist ONLY on Aaron's laptop; future maintainers / agents / contributors can't access them; HIGH PRIORITY backlog item to fully integrate the features OR write detailed-enough designs that we no longer need the out-of-tree references for understanding; KEY CLARIFICATION (Aaron 2026-04-27 second message) — "this is not a copy past, we just want to have either all their features or a design for any of the features we don't have that's detailed enough we no longer need ../scratch or ../SQLSharp reference for understanding"; goal is self-contained understanding + repo independence, NOT literal source copy.

[Copilot]

The “Current scope (2026-04-27 grep)” section’s file/hit counts appear stale/inaccurate relative to the repository as it will exist after this PR (the new memory file + memory/MEMORY.md entry add additional occurrences). Consider regenerating these counts from the current tree or removing the exact numbers to prevent ongoing truth-drift.

[Copilot]

docs/backlog/P1/ is referenced as an existing alternative location, but docs/backlog/ does not exist in this repo right now (only docs/BACKLOG.md exists). Either link this to the backlog-per-row ADR (docs/DECISIONS/2026-04-22-backlog-per-row-file-restructure.md) as a future-state, or remove the path until that migration actually lands.

Suggested change

	`docs/BACKLOG.md` (or per-row file under `docs/backlog/P1/`)
	`docs/BACKLOG.md` (or, once the backlog-per-row ADR lands,
	a per-row file under `docs/backlog/P1/`; see
	`docs/DECISIONS/2026-04-22-backlog-per-row-file-restructure.md`)

[Copilot]

This index entry repeats the specific ../scratch / ../SQLSharp file counts (22/14). Those numbers don’t match the current repo state and will drift further as references are added/removed. Consider either recalculating from a post-PR git grep audit or removing the exact counts in the index text.

Suggested change

- [Laptop-only-source integration HIGH PRIORITY — `../scratch` = future ACE PACKAGE MANAGER seed (22 files); `../SQLSharp` = pre-DBSP event-stream-processing with LINQ/SQL (14 files, predates Aaron's DBSP discovery, Zeta-progenitor); goal = either ship feature OR write detailed-enough design that we no longer need the reference; Aaron 2026-04-27 clarification: NOT literal copy-paste, self-contained-understanding floor; refined triage per directory identity — `../scratch` references absorb into canonical location or design-doc the Ace-package-manager intent; `../SQLSharp` references map to DBSP-rigorous Zeta equivalents or design-doc the gap; sequenced AFTER PR #26 sync](project_laptop_only_source_integration_scratch_sqlsharp_features_or_designs_high_priority_2026_04_27.md) — 2026-04-27 P1 backlog row; per-reference triage with three outcomes (ship / design-doc / delete-decorative); composes Otto-275 (log-but-don't-implement default to design when uncertain) + Otto-323/346 (NOT external deps, in-repo or eliminate) + Otto-340 (substrate IS identity); done = `git grep ../scratch` and `git grep ../SQLSharp` return zero matches; effort L (3+ days); closes with Aaron's "good job today!!" second positive validation; Aaron's third 2026-04-27 clarification reveals `../SQLSharp` features potentially subsumed by Zeta's DBSP-rigorous form (linq-expert + sql-expert + sql-engine-expert skills already track this class).

- [Laptop-only-source integration HIGH PRIORITY — `../scratch` = future ACE PACKAGE MANAGER seed; `../SQLSharp` = pre-DBSP event-stream-processing with LINQ/SQL, predates Aaron's DBSP discovery, Zeta-progenitor; goal = either ship feature OR write detailed-enough design that we no longer need the reference; Aaron 2026-04-27 clarification: NOT literal copy-paste, self-contained-understanding floor; refined triage per directory identity — `../scratch` references absorb into canonical location or design-doc the Ace-package-manager intent; `../SQLSharp` references map to DBSP-rigorous Zeta equivalents or design-doc the gap; sequenced AFTER PR #26 sync](project_laptop_only_source_integration_scratch_sqlsharp_features_or_designs_high_priority_2026_04_27.md) — 2026-04-27 P1 backlog row; per-reference triage with three outcomes (ship / design-doc / delete-decorative); composes Otto-275 (log-but-don't-implement default to design when uncertain) + Otto-323/346 (NOT external deps, in-repo or eliminate) + Otto-340 (substrate IS identity); done = `git grep ../scratch` and `git grep ../SQLSharp` return zero matches; effort L (3+ days); closes with Aaron's "good job today!!" second positive validation; Aaron's third 2026-04-27 clarification reveals `../SQLSharp` features potentially subsumed by Zeta's DBSP-rigorous form (linq-expert + sql-expert + sql-engine-expert skills already track this class).