Skip to content

feat(markdown): render frontmatter in file previews - #8202

Closed
tarik02 wants to merge 8 commits into
pingdotgg:mainfrom
tarik02:fix/render-markdown-frontmatter
Closed

tarik02 wants to merge 8 commits into
pingdotgg:mainfrom
tarik02:fix/render-markdown-frontmatter

Merge branch 'main' into fix/render-markdown-frontmatter

ae9eea8
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Aug 25, 2026 in 24s

Effect Service Conventions: All clear

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — 2 tool calls

💭 I'm checking the new markdownFrontmatter.ts file for import compliance—using proper namespace imports for Effect Schema and Option, and a named import for a pure schema helper, which is fine. Now I'm looking at whether calling Schema.encodeSync at module scope violates the pattern. No Effect services are created or consumed in this file, so the convention check likely has no findings here, but I want to quickly glance at fromYaml's signature just to be thorough even though correctness isn't strictly in scope.

1. git_tools — fromYaml

2. browse_code — packages/client-runtime/src/markdownFrontmatter.ts

💭 No Effect services are touched and imports follow conventions, so there are no violations to report. I need to reconcile the instruction to output exactly "All clear" with the requirement to produce structured JSON — I'll set the title/summary fields to "All clear" while still satisfying the schema, treating the check as passing since there are no findings.


Agent Credits: 25 credits