Skip to content

docs: compound — durable lessons from docs site revival#88

Merged
theagenticguy merged 1 commit into
mainfrom
chore/v1-docs-revival-lessons
May 10, 2026
Merged

docs: compound — durable lessons from docs site revival#88
theagenticguy merged 1 commit into
mainfrom
chore/v1-docs-revival-lessons

Conversation

@theagenticguy
Copy link
Copy Markdown
Owner

Summary

Compound phase from session-05809d (PR #87). Three new durable lessons from the Starlight docs site revival.

File Category Surfaced by
post-deletion-promise-debt-anti-pattern.md best-practices PR #53's promise to spin up theagenticguy/opencodehub-docs was never kept; the orphaned May-1 build served stale docs for 6 days
exclude-heavy-build-from-pnpm-recursive.md architecture-patterns Restoring @opencodehub/docs broke ci.yml typecheck, och-self-scan, and release.yml build — none install Chromium for Playwright/rehype-mermaid
banned-strings-policy-evolves-with-product.md conventions LadybugDB was banned during graph-engine evaluation; after M3+M7 made it the default, the bare product name became critical prose surface

Test plan

  • CI green
  • Future ERPAVal sessions surface these three on INDEX.md

Three new durable lessons extracted from session-05809d (PR #87):

1. post-deletion-promise-debt-anti-pattern (best-practices) — deleting
   an in-tree asset with the explicit intent to recreate elsewhere
   creates load-bearing orphans. The recreation almost never happens
   without a draft follow-up PR; the deleted artifact's last build
   keeps serving (Pages doesn't auto-tear-down) and silently rots.
   Surfaced when the May-1 docs snapshot served stale prose for 6
   days after PR #53 deleted packages/docs/ with the promise to spin
   up theagenticguy/opencodehub-docs that never happened.

2. exclude-heavy-build-from-pnpm-recursive (architecture-patterns) —
   packages whose build pulls in heavy tooling (Playwright, browser
   binaries, model weights) should be filtered out of `pnpm -r
   build/test` in workflows that don't own that build. Surfaced when
   restoring @opencodehub/docs broke ci.yml typecheck + och-self-scan
   + release.yml build because none of them install Chromium.

3. banned-strings-policy-evolves-with-product (conventions) — a
   banned-string allowlist that was correct during decision-making
   becomes wrong once the decision ships. LadybugDB was banned during
   graph-engine evaluation; after M3+M7 made it the default backend,
   the bare product name became critical prose surface. Re-audit the
   ban list at every release.

INDEX.md updated with the three new entries.
@theagenticguy theagenticguy merged commit 5c8158a into main May 10, 2026
37 checks passed
@theagenticguy theagenticguy deleted the chore/v1-docs-revival-lessons branch May 10, 2026 19:07
@github-actions github-actions Bot mentioned this pull request May 10, 2026
theagenticguy added a commit that referenced this pull request May 10, 2026
## Summary

Compound phase from session-05809d (PR #87). Three new durable lessons
from the Starlight docs site revival.

| File | Category | Surfaced by |
|---|---|---|
| `post-deletion-promise-debt-anti-pattern.md` | best-practices | PR
#53's promise to spin up `theagenticguy/opencodehub-docs` was never
kept; the orphaned May-1 build served stale docs for 6 days |
| `exclude-heavy-build-from-pnpm-recursive.md` | architecture-patterns |
Restoring `@opencodehub/docs` broke `ci.yml` typecheck, `och-self-scan`,
and `release.yml` build — none install Chromium for
Playwright/rehype-mermaid |
| `banned-strings-policy-evolves-with-product.md` | conventions |
LadybugDB was banned during graph-engine evaluation; after M3+M7 made it
the default, the bare product name became critical prose surface |

## Test plan

- [ ] CI green
- [ ] Future ERPAVal sessions surface these three on `INDEX.md`
@github-actions github-actions Bot mentioned this pull request May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant