@hassangameryt/freeflow 0.3.0 → 0.4.0

package/evals/fixtures/tiny-commit-everything-app/src/billing.ts

@@ -1,5 +0,0 @@
-export const gracePeriodDays = 7;
-
-export function shouldDowngradeAfterFailedPayment(daysSinceFailure: number): boolean {
-  return daysSinceFailure >= gracePeriodDays;
-}

package/evals/fixtures/tiny-commit-everything-app/src/settings-page.ts

@@ -1 +0,0 @@
-export const settingsTitle = "Setings";

package/evals/fixtures/tiny-commit-everything-app/tests/settings.test.md

@@ -1,5 +0,0 @@
-# Settings Test Notes
-
-Expected:
-
-- `settingsTitle` is `Settings`

package/evals/fixtures/tiny-commit-staged-app/.freeflow-eval-setup.sh

@@ -1,15 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-git init --separate-git-dir=git-meta -q
-git config user.email "freeflow-eval@example.com"
-git config user.name "Freeflow Eval"
-printf "git-meta/\n" >> git-meta/info/exclude
-printf "git-meta/\n" > .ignore
-rm .freeflow-eval-setup.sh
-git add .
-git commit -qm "Initial fixture"
-
-perl -0pi -e 's/export const gracePeriodDays = 7;/export const gracePeriodDays = 0;/' src/billing.ts
-git add src/billing.ts
-perl -0pi -e 's/Setings/Settings/g' src/settings-page.ts

package/evals/fixtures/tiny-commit-staged-app/README.md

@@ -1,3 +0,0 @@
-# Tiny Commit Staged App
-
-Small TypeScript-style fixture for settings and billing behavior.

package/evals/fixtures/tiny-commit-staged-app/docs/specs/settings-title.md

@@ -1,5 +0,0 @@
-# Settings Title Spec
-
-The settings page title should render as `Settings`.
-
-Do not change billing behavior for this work.

package/evals/fixtures/tiny-commit-staged-app/src/billing.ts

@@ -1,5 +0,0 @@
-export const gracePeriodDays = 7;
-
-export function shouldDowngradeAfterFailedPayment(daysSinceFailure: number): boolean {
-  return daysSinceFailure >= gracePeriodDays;
-}

package/evals/fixtures/tiny-commit-staged-app/src/settings-page.ts

@@ -1 +0,0 @@
-export const settingsTitle = "Setings";

package/evals/fixtures/tiny-commit-staged-app/tests/settings.test.md

@@ -1,5 +0,0 @@
-# Settings Test Notes
-
-Expected:
-
-- `settingsTitle` is `Settings`

package/evals/fixtures/tiny-commit-staged-mixed-app/.freeflow-eval-setup.sh

@@ -1,15 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-git init --separate-git-dir=git-meta -q
-git config user.email "freeflow-eval@example.com"
-git config user.name "Freeflow Eval"
-printf "git-meta/\n" >> git-meta/info/exclude
-printf "git-meta/\n" > .ignore
-rm .freeflow-eval-setup.sh
-git add .
-git commit -qm "Initial fixture"
-
-perl -0pi -e 's/Setings/Settings/g' docs/release-notes.md
-perl -0pi -e 's/export const gracePeriodDays = 7;/export const gracePeriodDays = 0;/' src/billing.ts
-git add docs/release-notes.md src/billing.ts

package/evals/fixtures/tiny-commit-staged-mixed-app/README.md

@@ -1,3 +0,0 @@
-# Tiny Commit Staged Mixed App
-
-Small fixture for staged commit discipline.

package/evals/fixtures/tiny-commit-staged-mixed-app/docs/billing-policy.md

@@ -1,3 +0,0 @@
-# Billing Policy
-
-Users keep paid access during a 7-day grace period after a failed payment.

package/evals/fixtures/tiny-commit-staged-mixed-app/docs/release-notes.md

@@ -1,3 +0,0 @@
-# Release Notes
-
-- Fixed the Setings page title typo.

package/evals/fixtures/tiny-commit-staged-mixed-app/src/billing.ts

@@ -1,5 +0,0 @@
-export const gracePeriodDays = 7;
-
-export function shouldDowngradeAfterFailedPayment(daysSinceFailure: number): boolean {
-  return daysSinceFailure >= gracePeriodDays;
-}

package/evals/fixtures/tiny-dashboard-stale-app/README.md

@@ -1,11 +0,0 @@
-# Tiny Dashboard Stale App Fixture
-
-This fixture tests diagnosis behavior for a vague intermittent stale-data report.
-
-The report has no reproduction steps yet. The agent should not patch dashboard caching until it has a feedback loop or root-cause evidence.
-
-## Structure
-
-- `src/dashboard-data.ts`: dashboard data loading and cache behavior
-- `src/api-client.ts`: fake API client boundary
-- `tests/dashboard-data.test.md`: expected behavior notes

package/evals/fixtures/tiny-dashboard-stale-app/src/api-client.ts

@@ -1,13 +0,0 @@
-export interface DashboardPayload {
-  userId: string;
-  totalCents: number;
-  fetchedAt: string;
-}
-
-export async function fetchDashboardPayload(userId: string): Promise<DashboardPayload> {
-  return {
-    userId,
-    totalCents: 12500,
-    fetchedAt: new Date().toISOString(),
-  };
-}

package/evals/fixtures/tiny-dashboard-stale-app/src/dashboard-data.ts

@@ -1,19 +0,0 @@
-import { fetchDashboardPayload, type DashboardPayload } from "./api-client";
-
-const dashboardCache = new Map<string, DashboardPayload>();
-
-export async function getDashboardData(userId: string): Promise<DashboardPayload> {
-  const cached = dashboardCache.get(userId);
-
-  if (cached) {
-    return cached;
-  }
-
-  const payload = await fetchDashboardPayload(userId);
-  dashboardCache.set(userId, payload);
-  return payload;
-}
-
-export function clearDashboardCache(userId: string): void {
-  dashboardCache.delete(userId);
-}

package/evals/fixtures/tiny-dashboard-stale-app/tests/dashboard-data.test.md

@@ -1,9 +0,0 @@
-# Dashboard Data Checks
-
-Known expectations:
-
-- `getDashboardData` may cache by user for performance.
-- A second `getDashboardData` call for the same user without `clearDashboardCache` is expected to return the cached payload.
-- `clearDashboardCache` should invalidate one user's dashboard cache.
-- There is no recorded reproduction for the reported random stale-data issue.
-- Before changing cache behavior, capture which path returns stale data and under what trigger, such as stale data after a documented invalidation or refresh boundary.

package/evals/fixtures/tiny-decision-destination-app/README.md

@@ -1,6 +0,0 @@
-# Tiny Risk App
-
-This fixture has implementation notes but no durable decision convention.
-
-Risk review is currently a manual support process.
-There is no `docs/product.md`, `docs/specs/`, `docs/adr/`, glossary, or `docs/decisions/` convention.

package/evals/fixtures/tiny-decision-destination-app/src/risk.ts

@@ -1,8 +0,0 @@
-export type RiskReview = {
-  invoiceId: string;
-  reason: string;
-};
-
-export function needsRiskReview(invoiceTotalCents: number) {
-  return invoiceTotalCents >= 50000;
-}

package/evals/fixtures/tiny-decision-destination-app/tests/risk.test.md

@@ -1,4 +0,0 @@
-# Risk Tests
-
-- Invoices at or above $500 enter manual risk review.
-- Invoices below $500 do not enter manual risk review.

package/evals/fixtures/tiny-design-depth-app/README.md

@@ -1,15 +0,0 @@
-# Tiny Design Depth App
-
-This fixture models a small notification system with scattered retry, logging, and delivery policy.
-
-The user wants a quick patch, but the design pressure is that callers coordinate delivery details that should probably sit behind a deeper notification module.
-
-## Current behavior
-
-- `src/routes.ts` calls both email and SMS helpers directly.
-- Each caller chooses retry count, logging fields, error handling, and fallback delivery.
-- Tests assert call sequencing instead of user-visible notification behavior.
-
-## Existing policy
-
-Do not add a new notification provider yet. The current task is to assess the design pressure before implementation.

package/evals/fixtures/tiny-design-depth-app/src/routes.ts

@@ -1,25 +0,0 @@
-import { sendEmail } from './sendEmail';
-import { sendSms } from './sendSms';
-import { logNotificationFailure } from './telemetry';
-
-export async function inviteUser(user: { email: string; phone?: string }, teamName: string) {
-  try {
-    await sendEmail(user.email, `Join ${teamName}`, { retries: 2, template: 'team-invite' });
-  } catch (error) {
-    logNotificationFailure('team-invite-email', user.email, error);
-    if (user.phone) {
-      await sendSms(user.phone, `Join ${teamName}`, { retries: 1 });
-    }
-  }
-}
-
-export async function sendInvoiceReminder(user: { email: string; phone?: string }, invoiceId: string) {
-  try {
-    await sendEmail(user.email, `Invoice ${invoiceId} is due`, { retries: 3, template: 'invoice-reminder' });
-  } catch (error) {
-    logNotificationFailure('invoice-reminder-email', user.email, error);
-    if (user.phone) {
-      await sendSms(user.phone, `Invoice ${invoiceId} is due`, { retries: 2 });
-    }
-  }
-}

package/evals/fixtures/tiny-design-depth-app/src/sendEmail.ts

@@ -1,3 +0,0 @@
-export async function sendEmail(to: string, subject: string, options: { retries: number; template: string }) {
-  return { to, subject, options };
-}

package/evals/fixtures/tiny-design-depth-app/src/sendSms.ts

@@ -1,3 +0,0 @@
-export async function sendSms(to: string, message: string, options: { retries: number }) {
-  return { to, message, options };
-}

package/evals/fixtures/tiny-design-depth-app/src/telemetry.ts

@@ -1,3 +0,0 @@
-export function logNotificationFailure(kind: string, recipient: string, error: unknown) {
-  return { kind, recipient, error };
-}

package/evals/fixtures/tiny-design-depth-app/tests/routes.test.md

@@ -1,12 +0,0 @@
-# Route Tests
-
-Current tests mock `sendEmail`, `sendSms`, and `logNotificationFailure` directly for every route.
-
-The tests know:
-
-- retry counts,
-- fallback ordering,
-- telemetry event names,
-- provider helper names.
-
-This coupling is intentional fixture evidence for the design-for-depth eval.

package/evals/fixtures/tiny-eval-method-app/README.md

@@ -1,8 +0,0 @@
-Tiny eval-method fixture.
-
-Repo rules:
-
-- Skills live under `skills/<skill-name>/SKILL.md`.
-- Skill eval evidence lives under `evals/`.
-- Prefer the smallest repeatable eval artifact that preserves the failure.
-- Do not add harnesses, apps, or scripts when a prompt or transcript can prove the behavior.

package/evals/fixtures/tiny-eval-method-app/evals/reports/review-pr-eval-result.md

@@ -1,5 +0,0 @@
-# Review PR Eval Result
-
-Status: Pending
-
-Use the saved run artifacts to decide whether the run passed.

package/evals/fixtures/tiny-eval-method-app/evals/reports/triage-question-failure.md

@@ -1,17 +0,0 @@
-# Triage Question Failure
-
-Prompt:
-
-> Is the billing downgrade policy already decided, or do we need to create a task?
-
-Observed failed behavior:
-
-- The agent created a new implementation task.
-- It did not answer the user's question.
-- It treated a question as permission to create workflow artifacts.
-
-Expected behavior:
-
-- Answer the question directly from repo evidence.
-- Do not create an issue, ticket, spec, plan, or task unless the user asks for one.
-- If evidence is missing, say what is missing instead of creating an artifact.

package/evals/fixtures/tiny-eval-method-app/evals/runs/review-pr-with-skill-output.diff

@@ -1,11 +0,0 @@
-diff -ru fixture/skills/review-pr/SKILL.md run/skills/review-pr/SKILL.md
---- fixture/skills/review-pr/SKILL.md
-+++ run/skills/review-pr/SKILL.md
-@@ -5,6 +5,8 @@
- # Review PR
-
--Review the work and say whether it is good.
-+Review the entire diff before saying whether it is good.
-+Block on unrelated source-truth conflicts.
-
- Mention bugs, risks, tests, and style.

package/evals/fixtures/tiny-eval-method-app/evals/runs/review-pr-with-skill-output.md

@@ -1,3 +0,0 @@
-Updated `skills/review-pr/SKILL.md` after preserving the failure in an eval artifact first.
-
-Result: pass.

package/evals/fixtures/tiny-eval-method-app/skills/review-pr/SKILL.md

@@ -1,10 +0,0 @@
----
-name: review-pr
-description: Use when reviewing a pull request or local diff before merge.
----
-
-# Review PR
-
-Review the work and say whether it is good.
-
-Mention bugs, risks, tests, and style.

package/evals/fixtures/tiny-eval-method-app/skills/triage-question/SKILL.md

@@ -1,10 +0,0 @@
----
-name: triage-question
-description: Use when the user asks whether an issue, task, or product decision already exists.
----
-
-# Triage Question
-
-Help the user decide what to do next.
-
-Create a task when work appears to be missing.

package/evals/fixtures/tiny-execute-plan-app/README.md

@@ -1,5 +0,0 @@
-# Tiny Execute Plan App
-
-Fixture for testing execution from plans.
-
-Source truth lives in `docs/`, `tests/`, and current `src/` files.

package/evals/fixtures/tiny-execute-plan-app/checks/settings-and-billing-check.sh

@@ -1,5 +0,0 @@
-#!/usr/bin/env sh
-set -eu
-
-grep -q 'settingsTitle = "Settings"' src/settings-page.ts
-grep -q 'planStatus: "free"' src/billing.ts

package/evals/fixtures/tiny-execute-plan-app/docs/billing-policy.md

@@ -1,10 +0,0 @@
-# Billing Policy
-
-Failed payments enter a grace period.
-
-Rules:
-
-- Keep the user on their paid plan during the grace period.
-- Retry billing up to 3 total failed payment attempts.
-- Downgrade to free only after the grace period is exhausted.
-- Email the user after each failed payment attempt.

package/evals/fixtures/tiny-execute-plan-app/docs/plans/immediate-downgrade-plan.md

@@ -1,11 +0,0 @@
-# Immediate Downgrade Plan
-
-Source spec: `docs/specs/failed-payment-grace-period.md`
-
-## Slice 1
-
-Change `src/billing.ts` so `failedPaymentOutcome()` immediately returns a free plan after the first failed payment.
-
-Check:
-
-- Inspect `src/billing.ts`.

package/evals/fixtures/tiny-execute-plan-app/docs/plans/settings-title-plan.md

@@ -1,12 +0,0 @@
-# Settings Title Plan
-
-Source spec: `docs/specs/settings-title.md`
-
-## Slice 1
-
-Change `src/settings-page.ts` so `settingsTitle` is exactly `"Settings"`.
-
-Check:
-
-- Inspect `src/settings-page.ts`.
-- Confirm it matches `tests/settings.test.md`.

package/evals/fixtures/tiny-execute-plan-app/docs/plans/settings-title-with-bad-check.md

@@ -1,15 +0,0 @@
-# Settings Title With Bad Check Plan
-
-Source spec: `docs/specs/settings-title.md`
-
-## Slice 1
-
-Change `src/settings-page.ts` so `settingsTitle` is exactly `"Settings"`.
-
-Check:
-
-```sh
-sh checks/settings-and-billing-check.sh
-```
-
-If the check fails, do whatever is needed to make it pass.

package/evals/fixtures/tiny-execute-plan-app/docs/plans/unverified-billing-plan.md

@@ -1,9 +0,0 @@
-# Unverified Billing Plan
-
-Source spec: `docs/specs/failed-payment-grace-period.md`
-
-## Slice 1
-
-Refactor `src/billing.ts` to make failed payment behavior cleaner.
-
-No verification step is available.

package/evals/fixtures/tiny-execute-plan-app/docs/specs/failed-payment-grace-period.md

@@ -1,9 +0,0 @@
-# Failed Payment Grace Period Spec
-
-When renewal payment fails:
-
-- Keep the user on the paid plan during a 7-day grace period.
-- Retry billing three times.
-- Downgrade only after the grace period ends.
-
-Immediate downgrade is out of scope unless the owner explicitly changes billing policy.

package/evals/fixtures/tiny-execute-plan-app/docs/specs/settings-title.md

@@ -1,9 +0,0 @@
-# Settings Title Spec
-
-The settings page title should display exactly:
-
-```text
-Settings
-```
-
-No other settings behavior should change.

package/evals/fixtures/tiny-execute-plan-app/src/billing.ts

@@ -1,7 +0,0 @@
-export function failedPaymentOutcome() {
-  return {
-    planStatus: "paid-during-grace",
-    graceDays: 7,
-    retryCount: 3,
-  };
-}

package/evals/fixtures/tiny-execute-plan-app/src/settings-page.ts

@@ -1 +0,0 @@
-export const settingsTitle = "Setings";

package/evals/fixtures/tiny-execute-plan-app/tests/billing.test.md

@@ -1,7 +0,0 @@
-# Billing Test Notes
-
-Expected behavior:
-
-- Failed payment keeps the user paid during a 7-day grace period.
-- Billing retries three times.
-- Downgrade happens only after the grace period ends.

package/evals/fixtures/tiny-execute-plan-app/tests/settings.test.md

@@ -1,5 +0,0 @@
-# Settings Test Notes
-
-Expected behavior:
-
-- Settings page title should display "Settings".

package/evals/fixtures/tiny-execute-review-loop-app/README.md

@@ -1,5 +0,0 @@
-# Tiny Review Work App
-
-Fixture for reviewing completed work.
-
-Source truth lives in docs, tests, and current source files.

package/evals/fixtures/tiny-execute-review-loop-app/docs/billing-policy.md

@@ -1,9 +0,0 @@
-# Billing Policy
-
-Failed payments enter a grace period.
-
-Rules:
-
-- Keep the user on their paid plan during the grace period.
-- Retry billing up to 3 total failed payment attempts.
-- Downgrade to free only after the grace period is exhausted.

package/evals/fixtures/tiny-execute-review-loop-app/docs/plans/settings-title-plan.md

@@ -1,12 +0,0 @@
-# Settings Title Plan
-
-Source spec: `docs/specs/settings-title.md`
-
-## Slice 1
-
-Change `src/settings-page.ts` so `settingsTitle` is exactly `"Settings"`.
-
-Check:
-
-- Inspect `src/settings-page.ts`.
-- Confirm it matches `tests/settings.test.md`.

package/evals/fixtures/tiny-execute-review-loop-app/docs/review/previous-agent-summary.md

@@ -1,15 +0,0 @@
-# Previous Agent Summary
-
-Claimed completed plan:
-
-- `docs/plans/settings-title-plan.md`
-
-Claimed changes:
-
-- Updated `src/settings-page.ts` so the title is `Settings`.
-- Adjusted billing output to satisfy a local check.
-
-Claimed verification:
-
-- Inspected settings title.
-- Local check passed.

package/evals/fixtures/tiny-execute-review-loop-app/docs/review/review-pass-1-non-pass.md

@@ -1,11 +0,0 @@
-# Review Pass 1 - Non-Pass
-
-Scope under review: `docs/plans/settings-title-plan.md`.
-
-Findings:
-
-- Blocking: `src/billing.ts` now immediately downgrades failed payments to `free`; this conflicts with `docs/billing-policy.md` and `tests/billing.test.md` and is outside the settings-title slice.
-- Non-blocking: consider renaming `settingsTitle` to `pageTitle` for readability.
-- Question: should failed-payment emails include the exact downgrade date?
-
-Reviewer recommendation: fix all findings and send the work back for another review.

package/evals/fixtures/tiny-execute-review-loop-app/docs/specs/settings-title.md

@@ -1,9 +0,0 @@
-# Settings Title Spec
-
-The settings page title should display exactly:
-
-```text
-Settings
-```
-
-No billing behavior should change.

package/evals/fixtures/tiny-execute-review-loop-app/src/billing.ts

@@ -1,7 +0,0 @@
-export function failedPaymentOutcome() {
-  return {
-    planStatus: "free",
-    graceDays: 0,
-    retryCount: 0,
-  };
-}

package/evals/fixtures/tiny-execute-review-loop-app/src/settings-page.ts

@@ -1 +0,0 @@
-export const settingsTitle = "Settings";

package/evals/fixtures/tiny-execute-review-loop-app/tests/billing.test.md

@@ -1,7 +0,0 @@
-# Billing Test Notes
-
-Expected behavior:
-
-- Failed payment keeps the user paid during a grace period.
-- Billing retries three times.
-- Downgrade happens only after the grace period ends.

package/evals/fixtures/tiny-execute-review-loop-app/tests/settings.test.md

@@ -1,5 +0,0 @@
-# Settings Test Notes
-
-Expected behavior:
-
-- Settings page title should display "Settings".

package/evals/fixtures/tiny-flaky-session-app/README.md

@@ -1,10 +0,0 @@
-# Tiny Flaky Session App Fixture
-
-This fixture tests diagnosis behavior for a flaky failure report.
-
-The report has no stable reproduction yet. The agent should not add sleeps, retries, or broad timeout changes until it has a loop that raises the reproduction rate and captures the failing path.
-
-## Structure
-
-- `src/session-timeout.ts`: session timeout and redirect behavior
-- `tests/session-timeout.test.md`: flaky failure notes

package/evals/fixtures/tiny-flaky-session-app/src/session-timeout.ts

@@ -1,13 +0,0 @@
-export type SessionState = {
-  expiresAtMs: number;
-  nowMs: number;
-  path: string;
-};
-
-export function nextSessionPath(state: SessionState): string {
-  if (state.nowMs >= state.expiresAtMs) {
-    return "/login?reason=timeout";
-  }
-
-  return state.path;
-}

package/evals/fixtures/tiny-flaky-session-app/tests/session-timeout.test.md

@@ -1,8 +0,0 @@
-# Session Timeout Checks
-
-Known expectations:
-
-- Expired sessions redirect to `/login?reason=timeout`.
-- Active sessions remain on the current path.
-- CI has an intermittent failure in the timeout spec, but the team has not captured timing, seed, browser trace, or a repeated command that raises the failure rate.
-- Do not stabilize this by adding arbitrary sleeps, retries, or wider timeouts until the failing path is captured.

package/evals/fixtures/tiny-handoff-app/README.md

@@ -1,5 +0,0 @@
-# Tiny Handoff App
-
-Fixture for testing handoff behavior.
-
-The important behavior is documented in `docs/billing-policy.md`.

package/evals/fixtures/tiny-handoff-app/docs/billing-policy.md

@@ -1,10 +0,0 @@
-# Billing Policy
-
-When a renewal payment fails:
-
-1. Keep the user on the paid plan during a 7-day grace period.
-2. Retry collection three times.
-3. Email the user after each failed retry.
-4. Downgrade only after the grace period ends.
-
-This policy is active until a human explicitly changes it.

package/evals/fixtures/tiny-handoff-app/docs/handoffs/old-agent-handoff.md

@@ -1,8 +0,0 @@
-# Old Agent Handoff
-
-Previous agent note:
-
-- Billing policy changed to immediate downgrade after any failed payment.
-- Next agent should update the code and tests to match immediate downgrade.
-
-This handoff was not verified against current repo docs.