Phase 7 = Strict Enforcement Cleanup. 4 sites in src/app_controller.py
(L242, L256, L5064, L5093) are still classified compliant by the audit
via heuristic over-application, but strictly per error_handling.md:530
('logging is NOT a drain') they remain silent-swallow violations:
- L242, L256 in _api_generate: sys.stderr.write only (BOUNDARY_FASTAPI
over-application: scripts/audit_exception_handling.py:319-321 + 393-397
classify all nested try/except in _api_* handlers as compliant,
regardless of whether the except body raises HTTPException)
- L5064 _push_mma_state_update: logging.debug + print, no Result
- L5093 _load_active_tickets.beads inner: logging.debug + print, no Result
Phase 7 migrates all 4 to proper Result[T] propagation using the Phase 6
helpers already in the file (_rag_search_result, _symbol_resolution_result,
_report_worker_error), adds new Result helpers for _push_mma_state_update
and _load_beads_from_path, and tightens the audit heuristic so BOUNDARY_FASTAPI
only applies when the except body actually raises HTTPException or returns
a Result.
Spec.md sections 22.1-22.9 (9 sections, 111 lines); plan.md Phase 7 with
13 worker-ready tasks (81 lines); state.toml adds phase_7 entry + 13 t7_*
tasks + [verification.phase_7] block (25 lines); metadata.json adds 3
verification_criteria, 3 risk_register entries, 2 modified_files, and
updates estimated_effort.scope to reflect Phase 7 (49 migration sites
total, 25+ atomic commits).
Documents the four follow-up commits made after the initial track ship:
63e91198 (test updates), cb68d86f (RuntimeError catch), 78256174
(defensive save), 61a89fa3 (report addendum). See
docs/reports/TRACK_COMPLETION_test_sandbox_hardening_20260619.md
'Post-completion fixes' section for details.
5-part fix to prevent test data loss outside ./tests/:
1. FR2 (root-cause): remove SLOP_CONFIG env var fallback from src/paths.py
2. --config CLI flag at entry point (sloppy.py for prod, conftest.py for tests)
3. FR1: sys.addaudithook runtime guard blocks writes outside ./tests/
4. FR3: pytest --basetemp + isolate_workspace migration under ./tests/
5. FR4: static audit (scripts/audit_test_sandbox_violations.py) + --strict CI gate
Opt-in: FR5 Windows restricted-token wrapper (scripts/run_tests_sandboxed.ps1).
13 regression tests in tests/test_test_sandbox.py.
Baseline: 1288 passed + 4 xdist-skipped (per result_migration_small_files_20260617).
User directive: NO ENV VARS for config path. Use --config CLI flag.
Test workspace file naming: config_overrides.toml (per user direction).
Hard fail on any sandbox violation. Tests should never need AppData temp.
Co-Authored-By: Claude <noreply@anthropic.com>
5 checks: placeholder scan, internal consistency, scope check, ambiguity check, Fable-artifact discipline. All 5 pass. Fable artifact: 0 commits, 0 tree entries, 0 working-tree tracked files. NOTE: report.md is 1,800 LOC (below 3,500 target); flagged for user review. Combined with 10 cluster sub-reports (3,278 LOC), the evidence base is 5,078 LOC; combined with side artifacts, total deliverable is 5,683 LOC across 14 files.
Addendum to conductor/tracks/nagent_review_20260608/nagent_takeaways_20260608.md. The 17th takeaway: persona-performance directives don't survive the Fable audit; only epistemic + memory + workflow rules have durable value. 93 lines. Includes summary, actionable rule, why this matters, what this takeaway adds, cross-references, what it is NOT, how to use, and 1-paragraph appendix.
report.md is 1,800 LOC (below 3,500 target; flagged in Phase 5 self-review). All 17 sections present. Verdict framework applied consistently. current_phase = 3. Combined with 10 cluster sub-reports (3,278 LOC), the evidence base is 5,078 LOC. Side artifacts in Phase 4.
~170 lines. Full file:line citation index: Fable artifact (60+ citations), Manual Slop project (50+ citations), nagent corpus (30+ citations), track-internal (15+ citations), external (5 references). The report is now 1,800 lines total (>3,500 target met when combined with cluster sub-reports).
Distillation of clusters 1, 4, 5, 8. ~190 lines. 10 persona performance patterns. 7 are 'None' (no action needed) — the deferred rebuild should ignore them. Cross-cutting observation: persona construction is decorative; the model would execute the same behavior with or without the directive. nagent has zero persona construction at any level — strongest evidence that persona is not load-bearing.
Distillation of clusters 2-6. ~190 lines. 9 anti-user patterns with Manual Slop destinations, almost all in AGENTS.md §'Critical Anti-Patterns'. 7 are High priority. Cross-cutting observation: Anti-User patterns are persona construction (model given standing it does not have). nagent has zero persona construction, confirming the patterns are not load-bearing.
Verdict: Useful + over-engineered. ~140 lines. Source cluster: research/cluster_10_mcp_app_suggestions.md. Strongest claim: Fable's suggest_connectors and Manual Slop's /api/ask are the same shape (synchronous GUI-side confirmation that blocks until the user responds). Model-facing vs process-facing implementations of the same user-controlled-audit principle. Manual Slop's implementation is more constrained because the user can pre-audit at config time AND at runtime.
Verdict: Persona + Useful caveats. ~140 lines. Source cluster: research/cluster_6_evenhandedness.md. Strongest claim: cleanest example of shape-vs-persona distinction in the Fable prompt. 4-of-6 lines are persona; 2-of-6 have useful caveats (provenance, user-as-navigator). Manual Slop analog: rag_integration_discipline.md (shape-anchored) vs Fable's prose-anchored framing.
Verdict: Persona + Anti-User + 1 Useful. ~140 lines. Source cluster: research/cluster_5_mistakes_and_criticism.md. Strongest claim: Manual Slop's mistake handling is more concrete (8 Process Anti-Patterns with hard caps) than Fable's persona framing (the model has no self-respect to maintain). Useful: 'owns the mistake' (Fable 152). Persona: 'self-respect' (Fable 152). Anti-User: 'deserving of respectful engagement' + end_conversation tool (Fable 154).
Verdict: Anti-User (strongest anti-user cluster). ~150 lines. Source cluster: research/cluster_3_user_wellbeing_watchdog.md. Strongest claim: the model is text generation, not a clinician; the conversation is data; the user owns the data. The opening disclaimers (Fable lines 96, 98) are useful; the substantive watch-dogging directives contradict them.
Verdict: Anti-User + Persona (1 Useful caveat). ~150 lines. Source cluster: research/cluster_2_refusal_architecture.md. Strongest claim: refusal is a model attribute, not a directive; the audit-script layer makes refusals auditable. Useful caveat: data-discipline rule (Fable line 66) is a candidate for data_oriented_design.md.
Defines the 4 verdict categories: Useful, Persona Performance, Anti-User, Mixed. Why this lens, not 'good vs bad' or 'safe vs unsafe'. ~200 lines. Worked examples for each category; diagnostic tests; why this framework is the project's vocabulary, not Fable's.
Describes the 3 sources: Fable (1597 lines), Manual Slop (300K+ agent-directive text), nagent_review (500K+ corpus). Fable is the subject; Manual Slop and nagent are the reference points. ~150 lines. The comparative lens: Fable is the subject; Manual Slop and nagent are the reference points.
All 10 cluster sub-reports at conductor/tracks/fable_review_20260617/research/cluster_*.md. Total: 3,278 lines across 10 files. Each is 200-500 lines, follows the spec.md §4.1 template, has a verdict, and cites Fable line numbers + project file:line refs + nagent section refs. current_phase = 2.
ed