@cryptotaxi247 / SquadScope-1 / commits / 9ffa9dd

Add 2026 yearly page with monthly cross-links (#526)

* docs: align pipeline docs with two-step analysis, SEO, and synthesis layout - README: document two-step Copilot CLI analysis (weekly-synthesis → weekly-analysis, both gpt-5.5), monthly synthesis layout with SEO titles/cross-links, and yearly narrative features - architecture.md: add two-step agent detail and additional analyze outputs - scripts/generate_rollups.py: add module docstring covering cross-links, SEO titles, structured frontmatter, and rolling report - scripts/generate_yearly_narrative.py: add module docstring covering SEO titles, meta descriptions, and monthly cross-links - scripts/month_synthesis.py: add module docstring covering frontmatter fields, body sections, summary constraints, and idempotent checksums Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: add data/analyzed/ prefix to output paths in docs Addresses Copilot review comments on PR #524 — correlations and press-context filenames now include the full directory path. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add 2026 yearly page with monthly cross-links Regenerate the yearly narrative page for 2026 so it includes cross-links to the May and June monthly reports. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix review comments: docstring terminology, path conflict, truncation artifacts, PR scope - Fix month_synthesis.py docstring: 'weakened' → 'weakening' to match field names - Remove content/yearly/2026/_index.md that conflicted with existing 2026.md - Merge improvements (summary field, monthly cross-links) into 2026.md - Fix truncation/punctuation artifacts in yearly narrative paragraph - PR description updated to reflect full change scope Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Juan Manuel Servera committed Jun 17, 2026 at 18:32 UTC 9ffa9ddf70042de8f238d840ad408e2a66b1f0e2
2 files changed +5 -2
content/yearly/2026.md
+4 -1
@@ -5,13 +5,16 @@ year: 2026
5 categories: ["yearly"]
6 months_covered: ["2026-05", "2026-06"]
7 format: "narrative"
8 +summary: "2026 has mainly been the year agent tooling stopped looking experimental and started behaving like infrastructure."
9 ---
10
11 ## Year in Review
12
13 +**Monthly reports:** [May](/monthly/2026/05/) · [June](/monthly/2026/06/)
14 +
15 2026 has mainly been the year agent tooling stopped looking experimental and started behaving like infrastructure. The ecosystem moved faster on capability than on trust. From May through June, the important change was not a parade of isolated repositories but the way a few categories kept hardening: agent skills as a real distribution layer, local and self-hosted execution as a durable buyer priority, and agent security as the main unresolved infrastructure gap. The year so far reads less like a sequence of weekly surprises and more like an ecosystem choosing its operating model.
16
14 -The monthly progression is clear: May set the initial tone when May 2026 reads less like three isolated weekly spikes and more like one continuous adjustment in priorities. The month opened with Week 21 shows real demand for agent infrastructure, but the trend data still lacks the baseline needed to separate…; June pushed the story further when June 2026 reads less like three isolated weekly spikes and more like one continuous adjustment in priorities. The month opened with Week 23 amplifies two W22 trends — agent memory infrastructure and skills verticalization — while a suspicious 56k-star self-hosted…. Taken together, those shifts show a market moving from experimentation toward packaging, distribution, and operating discipline. Even when the surface story changes from one month to the next, the deeper motion is cumulative rather than episodic.
17 +The monthly progression is clear: May set the initial tone as three weekly spikes merged into one continuous adjustment in priorities, with Week 21 showing real demand for agent infrastructure even as the trend data still lacked a solid baseline to separate signal from noise. June pushed the story further when Week 23 amplified two earlier trends — agent memory infrastructure and skills verticalization — while a surge of interest in self-hosted alternatives reinforced buyer demand for local control. Taken together, those shifts show a market moving from experimentation toward packaging, distribution, and operating discipline. Even when the surface story changes from one month to the next, the deeper motion is cumulative rather than episodic.
18
19 The category that hardened fastest was agent skills: what began as infrastructure and workflow plumbing started behaving like a market, then spread into more specific geographies, languages, and job-shaped use cases. Self-hosted and local-first tooling also matured from a cost or billing workaround into a control story about sovereignty, reliability, and execution on hardware teams already own. The prediction that capability would outrun trust was confirmed every month, because nothing in the visible tooling stack closed the gaps around agent isolation, prompt injection defense, or skills supply-chain auditing.
20
scripts/month_synthesis.py
+1 -1
@@ -5,7 +5,7 @@ artifact with:
5 - Structured frontmatter: title, summary, themes, persistent/accelerating/weakening
6 themes, key_gaps, top_repos, source_checksum, weeks_covered
7 - Body sections: Month Synthesis (narrative), Weekly Reports (cross-linked list),
8 - Trend Arc (persistent/accelerating/weakened theme bullets), Prediction Review
8 + Trend Arc (persistent/accelerating/weakening theme bullets), Prediction Review
9 - Summary field (≤28 words) suitable for SEO meta descriptions
10 - Source checksum for idempotent regeneration (skips if input unchanged)
11 """