feat(content): Tombstone v1.2 launch + publish-tracking records + CLAUDE.md restructure - #27
Open
sairam0424 wants to merge 15 commits into
Open
feat(content): Tombstone v1.2 launch + publish-tracking records + CLAUDE.md restructure#27sairam0424 wants to merge 15 commits into
sairam0424 wants to merge 15 commits into
Conversation
Adds full publish pipeline for trelix v2.4.0 first-user release: - Dev.to article (2,700w) — personal story angle, zero-infra pitch, seven retrieval legs, PR review + federated search features - Substack draft (same content, render via /tmp/render-substack-trelix.py) - Hashnode article (2,900w) — deeper architecture: 8-intent router, RRF mechanics, SPLADE/FLARE/HyDE explainers, v2.4.0 breaking change - Medium article (2,500w) — H2-only, no tables, Medium-optimised tone - LinkedIn: 15-slide carousel PDF (1.68MB @2x density) + post caption and text post copy; cover image 1400×787px All articles grounded in trelix README + CHANGELOG v2.4.0 facts.
Adds professional context from Anvilry profile across all 5 platform files: - Opening: AAVA Code (3K+ daily users, 5+ client envs) as the "both sides" framing for the code archaeology pain - Agentic section: Pensieve + Execution Engine (RAG+ReAct in production, 2K+ / 1.5K+ users) as credibility for FLARE + ReAct retrieval loop - MCP section: AAVA Code (150+ skills, 40+ tools) as the origin of the MCP integration design philosophy - Medium "what I got wrong": Pensieve production context before the call-graph resolver story LinkedIn post caption fully rewritten with production numbers woven in.
…cross all platforms
…x LinkedIn caption
Story: 'We Shipped v1.0. Then We Found Nine Bugs That Would Have Paged Us at 2am.' Covers v1.1.0 (Slack + Redis Streams + governance), v1.2.0 (resilience hardening — failsafe-go, idempotency keys, DLQ, distributed rate limiting), and v1.2.1 (critical fixes: kill switch broken, four-eyes unreachable, scheduler double-execution, Datadog auth silent fail). Platforms: Dev.to (draft-published), Substack (draft), Hashnode (draft), Medium (draft), LinkedIn caption
Publish-tracking records for already-shipped Tombstone v1.4 and Trelix v2/v2.9/v2.11 releases across devto/hashnode/linkedin/medium/substack.
Reorganizes into STORM pipeline stages, LLM fallback chains, path- resolution invariant, and web streaming architecture sections; tightens platform publishing rules; adds Branch Model & CI section. Also commits .husky/pre-commit (lint-staged hook).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
publish.tsfrontmatter parser to unescape embedded quotes correctlycontent/published/*tracking files for already-shipped Tombstone v1.4 and Trelix v2/v2.9/v2.11 releasesCLAUDE.mdarchitecture and publishing-rules documentationTest plan
fix/publish-frontmatter-unescape, PR fix(cli): unescape embedded quotes in publish frontmatter parser #25, which is a subset already opened separately)