femto-status

/femto:status

Read-only diagnostic. Use this to find out where a session is stuck or whether the gate is satisfied.

How to invoke

You need a session_id. If you don't have one in conversation, look at:

• The most recent femto_start_session response, OR
• The most recent .femto/session-*/ directory by mtime (the user can ls -lt .femto/).

Then call:

femto_get_session_status({ session_id: "<uuid>" })

What to render

Format the response as one short status line followed by an indented bullet list:

femto session <short-id> · phase=<phase> · allowed_to_emit=<yes|no>
  reads:
    - <read-id>: <state>[ — <validation_errors[0]>]
    - …
  probe coverage:
    - <kc-id>: <turns_so_far>/<min_required>
  grader: dispatched=<bool> · grader_md_present=<bool>
  errors:
    - <error[0]>
    - …

If allowed_to_emit is false, end with one of:

• next: invoke any reads with state in {missing, malformed} and retry validation — when phase is reads_pending and reads are bad.
• next: continue the Socratic probe (femto_advance_probe) — when phase is probe_active and coverage is incomplete.
• next: dispatch the femto-grader subagent (femto_request_grading) — when probe is terminated but grader hasn't run.
• next: see grader.md for per-KC reasoning — when grader.md exists but a required KC is below threshold.

If allowed_to_emit is true: gate satisfied; Edit/Write are unblocked for this session.