Completeness Scorecard

Every repository rated 0–100% across six metrics plus a holistic overall, from a July 2026 fleet audit. Use this as the honest counterweight to any aspirational prose elsewhere in the manual.

Metrics: Feature (scope built vs intended) · Quality (structure/typing) · Tests (automated coverage) · Docs · CI/CD (pipeline + deploy readiness) · Hardening (auth, errors, config, validation).

Scores (ranked)

#	Repo	Feat	Qual	Tests	Docs	CI/CD	Hard	Overall	Status
1	luke-forms	95	95	98	90	92	96	94	Ready
2	luke-email	90	91	94	92	93	92	93	Library
3	luke-agents	89	88	85	88	90	88	88	Ready
4	luke-auth-engine	90	88	85	82	85	92	88	Ready
5	luke-core-engine	90	88	86	83	89	91	88	Partial
6	luke-platform	88	88	82	90	85	91	88	Partial
7	luke-file-proxy	85	88	62	80	80	87	85	Partial
8	luke-consumer-ui	88	85	85	62	90	80	84	Partial
9	luke-signatures	85	88	62	90	85	78	81	Library
10	luke-workflow	72	87	82	85	85	76	81	Pre-launch
11	luke-api-collection	85	88	40	90	5	90	77	Partial
12	luke-analytics	70	88	82	85	78	55	76	Library
13	luke-core-ui	90	72	48	78	80	80	76	Partial
14	luke-lists	70	85	70	73	78	78	74	Library
15	luke-marketing-ui	87	85	0	78	5	45	66	Stale
16	luke-task-engine	58	72	8	65	5	35	41	Experimental

Not scored: luke-capability-engine, luke-signature-engine — empty shells merged into core-engine.

Fleet average overall ≈ 78%.

Recent uplifts

A hardening pass lifted four components toward production-ready:

• luke-email 87 → 93 — public-API-surface guard + size budget in CI, property/fuzz + injection-safety tests (email-core 39 → 66 tests), full docs suite. Now #2.
• luke-signatures 72 → 81 — added CI (it had none) + the API-surface/size gates, sign-core fuzz/edge tests, and SECURITY.md / docs/USAGE.md.
• luke-workflow 67 → 81 — added CI + gates + workflow-core property/fuzz tests + docs, and fixed a clean-checkout build-order bug + latent typecheck errors that had no CI to catch them.
• luke-file-proxy 82 → 85 — added a comprehensive README (it had only a design charter).

Every one is CI-green. The two library uplifts brought signatures and workflow up to the same enforceable gates as forms/email.

Tiers

• Production-grade (85–94): forms, email, agents, auth-engine, core-engine, platform, file-proxy.
• Solid, partial (76–84): consumer-ui, signatures, workflow, api-collection, analytics, core-ui.
• Emerging (74): lists.
• Stale / experimental: marketing-ui (66), task-engine (41) — the latter superseded by the engine's outbox/job-worker model.

Cross-fleet patterns

• Hardening is a fleet-wide strength — 85+ on every shipped service (fail-fast guards, tenant isolation, supply-chain scans). See Security.
• Testing is the most uneven axis — elite on test-first libraries (forms 98, email / agents / analytics 82–85) but thin on the UIs (core-ui 48, marketing-ui 0). The extracted libs signatures and workflow now carry -core fuzz suites; their React layers remain the frontier. See Testing.
• CI is now near-universal — the last two libraries without a pipeline (signatures, workflow) were wired up with the same API-surface + size gates as forms/email. Only marketing-ui (not a git repo) and the deprecated task-engine lack CI.
• Docs improving — file-proxy now has a README; consumer-ui (62) is the main remaining under-documented large surface.

Highest-impact fixes (remaining)

1. Test coverage on the React layers of luke-signatures / luke-workflow (~2k LOC each, hard to test under jsdom + react-pdf / react-flow) and broaden luke-core-ui e2e.
2. Refresh the stale Clerk → WorkOS mention in luke-auth-engine's README.
3. Push luke-lists / luke-analytics to GitHub (local-only today) so they get CI + the gates.
4. Decide luke-task-engine's fate — archive or delete (superseded, dead weight).

Method

Scores come from an evidence-based audit of each repo (README, build files, CI, test counts, LOC, git recency, deploy config). They are directional engineering judgments, not a substitute for reading the code.