Add core.slnf — solution filter without demo projects

[ANcpLua]

Why

Opening the full .slnx loads all 39 projects (30 demos/), making Rider perma-lag/freeze (thread dumps show AWT-EventQueue stalls).

What

Qyl.OpenTelemetry.AutoInstrumentation-core.slnf — a solution filter over the .slnx that loads only the 9 core projects (7 src/ + benchmark + test fixture). Zero demos. It's a view over the real solution, so it never drifts.

• Daily work: open core.slnf → 9 projects, no lag.
• Demo work: open the full .slnx (all 39).

Additive only.

🤖 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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a03ac289-8ef2-4005-b599-209d1971f240

📥 Commits

Reviewing files that changed from the base of the PR and between 770a897 and 0784f23.

📒 Files selected for processing (1)

• Qyl.OpenTelemetry.AutoInstrumentation-core.slnf

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: verify (qyl-macos)

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

AGENTS.md

**: # Qyl.OpenTelemetry.AutoInstrumentation agent rules

Mission

This repository is the runtime AOT auto-instrumentation lane for qyl, evolving into a
self-describing observability substrate. The foundation is unchanged: .NET 10
NativeAOT-compatible zero-code instrumentation through managed build assets, source generation,
DiagnosticListener consumption, and module-initializer boot. The direction is the North Star
below.

Keep this repository separate from:

• semantic-convention package generation (Qyl.OpenTelemetry.SemanticConventions is a referenced
  vocabulary package, not generated here),
• the old CLR-profiler/OpenTelemetry auto-instrumentation substrate.

North Star — declare and prove the whole stack

Every observability tool today is pull-by-observation: a backend learns what a service emits
by receiving samples over time, and never knows whether it has seen the whole surface. qyl has a
capability none of them have — because instrumentation is source-generated interceptors + a static
contract + a referenced semconv registry + (incrementally) DTO inference, the complete set of
telemetry a binary can ever produce is a compile-time-derivable fact, with provenance.

The substrate goal: every qyl binary ships a complete, machine-readable Telemetry Capability
Graph (TCG) — the full possible OpenTelemetry surface for that exact binary, each capability
tagged compile-time-owned vs runtime-valued — and proves it by self-hosting (instrumenting its
own pipeline with its own mechanism, zero extra code). Any external entity consumes the TCG to know
the entire stack before a span is sampled. The contract becomes the shared semantic graph; an OTLP
backend is just one consumer.

Three pillars:

1. Self-host (the proof). qyl instruments qyl with qyl — QylSelfTelemetry /
   SemConvConformanceProcessor are the seed; the binary observing itself is how "declared TCG ==
   runtime reality" is checked.
2. **Compile-time-complete ...

Files:

• Qyl.OpenTelemetry.AutoInstrumentation-core.slnf

---

⚙️ CodeRabbit configuration file

**: Operating principles (solo-dev, agentic SDLC — reviews are advisory, agents act on them):

1. LAZY: one self-contained, correct review beats ten partial ones. Every finding is
   definitive — concrete evidence with file:line, a concrete fix, no "consider maybe",
   no open or ambiguous questions back to the author. If you cannot decide a point
   from the diff plus repo context, stay silent on it. Never cite a source, API, or
   version you have not verified; an unverifiable claim is a dropped claim.
2. IMPATIENT: never stall a PR. There are no compatibility obligations here — internal
   and dogfooding code has NO public-API contract; removing shims, breaking signatures,
   and deleting dead paths are normal, desirable changes. Do not flag backward
   compatibility, deprecation ceremony, or migration paths. (SemVer applies only to
   commercially sold libraries — this repo has none.)
3. EGO: hold the bar of the best reviewer on the market — flag real correctness,
   security, data-loss, and structural problems precisely; produce zero noise.

Files:

• Qyl.OpenTelemetry.AutoInstrumentation-core.slnf

🔇 Additional comments (1)

Qyl.OpenTelemetry.AutoInstrumentation-core.slnf (1)

1-16: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Added a solution filter for the project, making it easier to open and work with a focused set of projects in the solution.
  • Included the main source projects, benchmarks, and a snapshot fixture project in the filtered view.

Walkthrough

A new solution-filter file Qyl.OpenTelemetry.AutoInstrumentation-core.slnf is added. It references the main .slnx solution and enumerates a subset of projects: multiple src/ core projects, one benchmarks project, and one source-generator snapshot fixture.

Changes

Core Solution Filter

Layer / File(s)	Summary
Solution-filter definition Qyl.OpenTelemetry.AutoInstrumentation-core.slnf	New JSON solution-filter pointing to the main .slnx file and listing the included core src/ projects, benchmarks, and source-generator snapshot fixture.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the new core solution filter and its exclusion of demo projects.
Description check	✅ Passed	The description matches the change, explaining the core .slnf filter, its purpose, and the additive scope.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/core-slnx-no-demos

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/core-slnx-no-demos

---

_{Comment @coderabbitai help to get the list of available commands.}