Close the parity go/no-go checklist from the 2026-07-19 handoff
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- ai, documentation, testing-qa
Research direction
Start with the pending-flight checklist and compare the capability statements in the README and docs with the evidence already available. Run each narrow validation flight, capturing the named run URL, receipt artifact, or issue comment; done means every box has durable evidence and any untested surface is explicitly documented.
Written by the indexing model from the issue text.
Description
Validation flights that are still missing before the platform's capability claims are backed by live evidence rather than by tests alone. Keep each flight small and purpose-built — a narrow run is faster to diagnose and produces clearer evidence than a broad fixture.
Pending flights
- Security projection: one qualifying and one non-qualifying finding. Only the qualifying one may create exactly one redacted, deduplicated issue.
- Learning ratchet, full loop: approve one safe skill or rule proposal → immutable activation → canary passes → a later run demonstrably receives it. Only the proposal half has been observed live.
- Guard candidate: an approved candidate becomes a task that travels through architect and builder rather than modifying the repository directly.
- Repo lane artifacts: a green doctor receipt and a signed integrity-check artifact captured from a repository-lane run.
- Skill isolation: re-capture project/org isolation with a freshly published skill.
Acceptance
- Every box above links durable evidence (run URL, receipt artifact, or issue comment).
- Capability statements in the README and docs match that evidence, and any surface that was not exercised is named explicitly rather than implied.
- Dominant language
- TypeScript
- Stars
- 71
- Forks
- 64
- Avg merge
- 15h 38m
- Merged PRs (30d)
- 66
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from theam/facility
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·