TheAngryByrd / TheAngryByrd/fsharp2
Implement the first governed performance runner cell
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Question
Can a Windows x64 controlled runner execute one pinned IcedTasks TFM through Cold Compilation and both mandatory Warm edits end to end under perf-governance-v1, including the immutable schedule, exact attempt/series statistics, admission and scanner controls, request/service/cache/project lineage, multi-process diagnostic replay, R3/R2/S1 evidence reconstruction, and fail-closed verdict reconciliation, while exposing portable adapter seams for later RID-matrix expansion?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing perf-governance-v1 surfaces and the Windows x64 runner path, then trace the pinned IcedTasks TFM through Cold Compilation and both Warm edits. Done requires end-to-end execution with the specified controls, statistics, lineage, replay, evidence reconstruction, and fail-closed verdict reconciliation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- performance, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100