wehub-resource-sync
26382a7ac6
CI / Test (macos-latest) (push) Waiting to run
CI / Test (ubuntu-latest) (push) Waiting to run
CI / Test (windows-latest) (push) Waiting to run
CI / Clippy (push) Waiting to run
CI / Build (no embeddings / no ORT) (push) Waiting to run
CI / Format (push) Waiting to run
CI / Cookbook (Node) (push) Waiting to run
CI / Pi Extension (Node) (push) Waiting to run
CI / Rust SDK (lean-ctx-client) (push) Waiting to run
CI / Embed SDK (lean-ctx-sdk) (push) Waiting to run
CI / Python SDK (leanctx) (push) Waiting to run
CI / Hermes Plugin (Python) (push) Waiting to run
CI / SDK Conformance Matrix (push) Waiting to run
CI / Coverage (push) Waiting to run
CI / cargo-deny (push) Waiting to run
CI / Adversarial Safety (push) Waiting to run
CodeQL / Analyze (javascript-typescript) (push) Waiting to run
JetBrains Plugin / Actionlint (push) Waiting to run
CI / Benchmarks (push) Waiting to run
CI / Output-Quality Gate (eval A/B) (push) Waiting to run
CI / Documentation (push) Waiting to run
CI / CI Green (push) Blocked by required conditions
CodeQL / Analyze (actions) (push) Waiting to run
CodeQL / Analyze (rust) (push) Waiting to run
JetBrains Plugin / Validation (push) Waiting to run
JetBrains Plugin / Build (push) Waiting to run
JetBrains Plugin / Test (push) Blocked by required conditions
Security Check / Security Scan (push) Waiting to run
specs/ — Spec-Driven Development (SDD)
lean-ctx develops non-trivial features spec-anchored (2026 SDD): the spec is the source of truth for intent; code + tests enforce it. Never jump spec → code — review the plan, then the tasks, then implement in small, verified steps.
Loop
spec → plan → tasks → implement (impact-first) → verify → evidence
See CONTRIBUTING.md → "Spec-driven workflow".
Layout
specs/_template/— copy these into a new feature dir.specs/NNN-<slug>/— one directory per feature;NNN= tracking issue iid.spec.md— problem, goal, EARS acceptance criteria, out-of-scope.plan.md— architecture, constraints, file structure, impact.tasks.md— atomic, individually testable steps with verification.
How this relates to existing docs (no duplication)
docs/contracts/*-v1.md— versioned runtime contracts (SSOT for behavior). Unchanged; a spec may touch a contract but does not replace it.docs/superpowers/— prior design notes/plans; kept as history, not migrated.specs/NNN-*— canonical home for new feature work going forward.
Conventions
- One feature = one
specs/NNN-<slug>/dir; keep the spec to 1–3 pages. - Acceptance criteria in EARS (
WHEN … THE system SHALL …). - Cite the spec in commits:
refs specs/NNN-<slug>. - Link the tracking issue (#NNN); the approved approach lives in
plan.md. - Skip the full loop for trivial fixes; use it for features, contracts, and anything touching the tool/CLI surface.