Workspace lab notebook for long-running or resumable research work.

Use this file to track chronology, not release notes. Keep entries short, factual, and operational.

• Objective: ...
• Changed: ...
• Verified: ...
• Failed / learned: ...
• Blockers: ...
• Next: ...

• Objective: Set up a deep research workflow for scaling laws.
• Changed: Created plan artifact at outputs/.plans/scaling-laws.md; defined 4 disjoint researcher dimensions and acceptance criteria.
• Verified: Read CHANGELOG.md and checked prior memory for related plan scaling-laws-implications.
• Failed / learned: No prior run-specific changelog entries existed beyond the template.
• Blockers: Waiting for user confirmation before launching researcher round 1.
• Next: On confirmation, spawn 4 parallel researcher subagents and begin evidence collection.

• Objective: Complete T4 on inference/test-time scaling and reasoning-time compute, scoped to 2023–2026.
• Changed: Wrote notes/scaling-laws-research-inference.md; updated outputs/.plans/scaling-laws.md to mark T4 done and log the inference-scaling verification pass.
• Verified: Cross-read 13 primary/official sources covering Tree-of-Thoughts, PRMs, repeated sampling, compute-optimal test-time scaling, provable laws, o1, DeepSeek-R1, s1, verifier failures, Anthropic extended thinking, and OpenAI reasoning API docs.
• Failed / learned: OpenAI blog fetch for learning-to-reason-with-llms returned malformed content, so the note leans on the o1 system card and API docs instead of that blog post.
• Blockers: T2 and T5 remain open before final synthesis; no single unified law for inference-time scaling emerged from public sources.
• Next: Complete T5 implications synthesis, then reconcile T3/T4 with foundational T2 before drafting the cited brief.

• Objective: Synthesize the four research notes into a single user-facing draft brief for the scaling-laws workflow.
• Changed: Wrote outputs/.drafts/scaling-laws-draft.md with an executive summary, curated reading list, qualitative meta-analysis, core-paper comparison table, explicit training-vs-inference distinction, and numbered inline citations with direct-URL sources.
• Verified: Cross-checked the draft against notes/scaling-laws-research-foundations.md, notes/scaling-laws-research-revisions.md, notes/scaling-laws-research-inference.md, and notes/scaling-laws-research-implications.md to ensure the brief explicitly states the literature is too heterogeneous for a pooled effect-size estimate.
• Failed / learned: The requested temp-run context.md and plan.md were absent, so the synthesis used outputs/.plans/scaling-laws.md plus the four note files as the working context.
• Blockers: Citation/claim verification pass still pending; this draft should be treated as pre-verification.
• Next: Run verifier/reviewer passes, then promote the draft into the final cited brief and provenance sidecar.

• Objective: Deliver a paper guide and qualitative meta-analysis on AI scaling laws.
• Changed: Finalized outputs/scaling-laws.md and sidecar outputs/scaling-laws.provenance.md; rendered preview PDF at outputs/scaling-laws.pdf; updated plan ledger and verification log in outputs/.plans/scaling-laws.md.
• Verified: Ran a reviewer pass recorded in notes/scaling-laws-verification.md; spot-checked key primary papers via alpha-backed reads for Kaplan 2020, Chinchilla 2022, and Snell 2024; confirmed PDF render output exists.
• Failed / learned: A pooled statistical meta-analysis would be misleading because the literature mixes heterogeneous outcomes, scaling axes, and evaluation regimes; final deliverable uses a qualitative meta-analysis instead.
• Blockers: None for this brief.
• Next: If needed, extend into a narrower sub-survey (e.g. only pretraining laws, only inference-time scaling, or only post-Chinchilla data-quality revisions).

• Objective: Let users download the Feynman research skills without installing the full terminal runtime.
• Changed: Added standalone skills-only installers at scripts/install/install-skills.sh and scripts/install/install-skills.ps1; synced website-public copies; documented user-level and repo-local install flows in README.md, website/src/content/docs/getting-started/installation.md, and website/src/pages/index.astro.
• Verified: Ran sh -n scripts/install/install-skills.sh; ran node scripts/sync-website-installers.mjs; ran cd website && npm run build; executed sh scripts/install/install-skills.sh --dir <tmp> and confirmed extracted SKILL.md files land in the target directory.
• Failed / learned: PowerShell installer behavior was not executed locally because PowerShell is not installed in this environment.
• Blockers: None for the Unix installer flow; Windows remains syntax-only by inspection.
• Next: If users want this exposed more prominently, add a dedicated docs/reference page and a homepage-specific skills-only CTA instead of a text link.

• Objective: Remove the moving edge installer channel and unify installs on tagged releases only.
• Changed: Updated scripts/install/install.sh, scripts/install/install.ps1, scripts/install/install-skills.sh, and scripts/install/install-skills.ps1 so the default target is the latest tagged release, latest-version resolution uses public GitHub release pages instead of api.github.com, and explicit edge requests now fail with a removal message; removed the release-edge job from .github/workflows/publish.yml; updated README.md and website/src/content/docs/getting-started/installation.md; re-synced website/public/install*.
• Verified: Ran sh -n on the Unix installer copies; confirmed sh scripts/install/install.sh edge and sh scripts/install/install-skills.sh edge --dir <tmp> fail with the intended removal message; executed sh scripts/install/install.sh into temp dirs and confirmed the installed binary reports 0.2.14; executed sh scripts/install/install-skills.sh --dir <tmp> and confirmed extracted SKILL.md files; ran cd website && npm run build.
• Failed / learned: The install failure was caused by unauthenticated GitHub API rate limiting on the edge path, so renaming channels without removing the API dependency would not have fixed the root cause.
• Blockers: npm run build still emits a pre-existing duplicate-content warning for getting-started/installation; the build succeeds.
• Next: If desired, remove the now-unused stable alias too and clean up the duplicate docs-content warning separately.

• Objective: Make the non-Anthropic subagent/auth fixes and contributor-guide updates releasable to tagged-install users instead of leaving them only on main.
• Changed: Bumped the package version from 0.2.14 to 0.2.15 in package.json and package-lock.json; updated pinned installer examples in README.md and website/src/content/docs/getting-started/installation.md; aligned the local-development docs example to the npm-based root workflow; added CONTRIBUTING.md plus the bundled skills/contributing/SKILL.md.
• Verified: Confirmed the publish workflow keys off package.json versus the currently published npm version; confirmed local npm test, npm run typecheck, and npm run build pass before the release bump.
• Failed / learned: The open subagent issue is fixed on main but still user-visible on tagged installs until a fresh release is cut.
• Blockers: Need the GitHub publish workflow to finish successfully before the issue can be honestly closed as released.
• Next: Push 0.2.15, monitor the publish workflow, then update and close the relevant GitHub issue/PR once the release is live.

• Objective: Debug why tagged installs can still fail subagent/auth flows after 0.2.15 when users are not on Anthropic.
• Changed: Added scripts/lib/pi-subagents-patch.mjs plus type declarations and wired scripts/patch-embedded-pi.mjs to rewrite vendored pi-subagents runtime files so they resolve user-scoped paths from PI_CODING_AGENT_DIR instead of hardcoded ~/.pi/agent; added tests/pi-subagents-patch.test.ts.
• Verified: Materialized .feynman/npm, inspected the shipped [email protected] sources, confirmed the hardcoded ~/.pi/agent paths in index.ts, agents.ts, artifacts.ts, run-history.ts, skills.ts, and chain-clarify.ts; ran node scripts/patch-embedded-pi.mjs; ran npm test, npm run typecheck, and npm run build.
• Failed / learned: The earlier 0.2.15 fix only proved that Feynman exported PI_CODING_AGENT_DIR to the top-level Pi child; it did not cover vendored extension code that still hardcoded .pi paths internally.
• Blockers: Users still need a release containing this patch before tagged installs benefit from it.
• Next: Cut the next release and verify a tagged install exercises subagents without reading from ~/.pi/agent.

• Objective: Ship the vendored pi-subagents agent-dir compatibility fix to tagged installs.
• Changed: Bumped the package version from 0.2.15 to 0.2.16 in package.json and package-lock.json; updated pinned installer examples in README.md and website/src/content/docs/getting-started/installation.md.
• Verified: Re-ran npm test, npm run typecheck, and npm run build; ran cd website && npm run build; ran npm pack and confirmed the 0.2.16 tarball includes the new scripts/lib/pi-subagents-patch.* files.
• Failed / learned: An initial local build:native-bundle check failed because npm pack and build:native-bundle were run in parallel, and prepack intentionally removes dist/release; rerunning npm run build:native-bundle sequentially succeeded.
• Blockers: None in the repo; publishing still depends on the GitHub workflow running on the bumped version.
• Next: Push the 0.2.16 release bump and monitor npm/GitHub release publication.

• Objective: Triage open Pi-related issues/PRs, fix the concrete package update regression, and refresh Pi dependencies against current upstream releases.
• Changed: Pinned direct package-manager operations (feynman update, feynman packages install) to Feynman's npm prefix by exporting FEYNMAN_NPM_PREFIX, NPM_CONFIG_PREFIX, and npm_config_prefix before invoking Pi's DefaultPackageManager; bumped @mariozechner/pi-ai and @mariozechner/pi-coding-agent from 0.62.0 to 0.64.0; adapted src/model/registry.ts to the new ModelRegistry.create(...) factory; integrated PR #15's /feynman-model command on top of current main.
• Verified: Ran npm test, npm run typecheck, and npm run build successfully after the dependency bump and PR integration; confirmed upstream [email protected] still uses npm install -g for user-scope package updates, so the Feynman-side prefix fix is still required.
• Failed / learned: PR #14 is a stale branch with no clean merge path against current main; the only user-facing delta is the ValiChord prompt/skill addition, and the branch also carries unrelated release churn plus demo-style material, so it was not merged in this pass.
• Blockers: None in the local repo state; remote merge/push still depends on repository credentials and branch policy.
• Next: If remote write access is available, commit and push the validated maintenance changes, then close issue #22 and resolve PR #15 as merged while leaving PR #14 unmerged pending a cleaned-up, non-promotional resubmission.

• Objective: Finish the remaining high-confidence open tracker items after the Pi 0.64.0 upgrade instead of leaving the issue list half-reconciled.
• Changed: Added a Windows extension-loader patch helper so Feynman rewrites Pi extension imports to file:// URLs on Windows before interactive startup; added /commands, /tools, and /capabilities discovery commands and surfaced /hotkeys plus /service-tier in help metadata; added explicit service-tier support via feynman model tier, --service-tier, status/doctor output, and a provider-payload hook that passes service_tier only to supported OpenAI/OpenAI Codex/Anthropic models; added Exa provider recognition to Feynman's web-search status layer and vendored pi-web-access.
• Verified: Ran npm test, npm run typecheck, and npm run build; smoke-imported the modified vendored pi-web-access modules with node --import tsx.
• Failed / learned: The remaining ValiChord PR is still stale and mixes a real prompt/skill update with unrelated branch churn; it is a review/triage item, not a clean merge candidate.
• Blockers: No local build blockers remain; issue/PR closure still depends on the final push landing on main.
• Next: Push the verified cleanup commit, then close issues fixed by the dependency bump plus the new discoverability/service-tier/Windows patches, and close the stale ValiChord PR explicitly instead of leaving it open indefinitely.

• Objective: Fix Windows startup failures where feynman exits before the Pi child process initializes.
• Changed: Converted the Node preload module paths passed via node --import in src/pi/launch.ts to file:// specifiers using a new toNodeImportSpecifier(...) helper in src/pi/runtime.ts; expanded scripts/patch-embedded-pi.mjs so it also patches the bundled workspace copy of Pi's extension loader when present.
• Verified: Added a regression test in tests/pi-runtime.test.ts covering absolute-path to file:// conversion for preload imports; ran npm test, npm run typecheck, and npm run build.
• Failed / learned: The raw Windows ERR_UNSUPPORTED_ESM_URL_SCHEME stack is more consistent with Node rejecting the child-process --import C:\\... preload before Pi starts than with a normal in-app extension load failure.
• Blockers: Windows runtime execution was not available locally, so the fix is verified by code path inspection and automated tests rather than an actual Windows shell run.
• Next: Ask the affected user to reinstall or update to the next published package once released, and confirm the Windows REPL now starts from a normal PowerShell session.

• Objective: Triage the open repo backlog, land the highest-signal fixes locally, and add guardrails against stale promotional workflow content.
• Changed: Hardened Windows launch paths in bin/feynman.js, scripts/build-native-bundle.mjs, and scripts/install/install.ps1; set npm prefix overrides earlier in scripts/patch-embedded-pi.mjs; added a pi-web-access runtime patch helper plus FEYNMAN_WEB_SEARCH_CONFIG env wiring so bundled web search reads the same ~/.feynman/web-search.json that doctor/status report; taught src/pi/web-access.ts to honor the legacy route key; fixed bundled skill references and expanded the skills-only installers/docs to ship the prompt and guidance files those skills reference; added regression tests for config paths, catalog snapshot edges, skill-path packaging, pi-web-access patching, and blocked promotional content.
• Verified: Ran npm test, npm run typecheck, and npm run build successfully after the full maintenance pass.
• Failed / learned: The skills-only install issue was not just docs drift; the shipped SKILL.md files referenced prompt paths that only made sense after installation, so the repo needed both path normalization and packaging changes.
• Blockers: Remote issue/PR closure and merge actions still depend on the final reviewed branch state being pushed.
• Next: Push the validated fixes, close the duplicate Windows/reporting issues they supersede, reject the promotional ValiChord PR explicitly, and then review whether the remaining docs-only or feature PRs should be merged separately.

• Objective: Run a deeper install/security verification pass against the post-cleanup 0.2.17 tree instead of assuming the earlier targeted fixes covered the shipped artifacts.
• Changed: Reworked extensions/research-tools/header.ts to use @mariozechner/pi-tui width-aware helpers for truncation/wrapping so wide Unicode text does not overflow custom header rows; changed src/pi/launch.ts to stop mirroring child crash signals back onto the parent process and instead emit a conventional exit code; added FEYNMAN_INSTALL_SKILLS_ARCHIVE_URL overrides to the skills installers for pre-release smoke testing; aligned root and website dependency trees with patched transitive versions using npm overrides; fixed src/pi/web-access.ts so search status respects FEYNMAN_HOME semantics instead of hardcoding the current shell home directory; added tests/pi-launch.test.ts.
• Verified: Ran npm test, npm run typecheck, npm run build, cd website && npm run build, npm run build:native-bundle; smoke-tested scripts/install/install.sh against a locally served dist/release/feynman-0.2.17-darwin-arm64.tar.gz; smoke-tested scripts/install/install-skills.sh against a local source archive; confirmed installed feynman --version, feynman --help, feynman doctor, and packaged feynman search status work from the installed bundle; npm audit --omit=dev is clean in the root app and website after overrides.
• Failed / learned: The first packaged search status smoke test still showed the user home path because the native bundle had been built before the FEYNMAN_HOME path fix; rebuilding the native bundle resolved that mismatch.
• Blockers: PowerShell runtime was unavailable locally, so Windows installer execution remained code-path validated rather than actually executed.
• Next: Push the second-pass hardening commit, then keep issue #46 and issue #47 open until users on the affected Linux/CJK environments confirm whether the launcher/header fixes fully resolve them.

• Objective: Reduce the remaining open tracker items by landing the lowest-risk missing docs/catalog updates and a targeted Cloud Code Assist compatibility patch instead of only hand-triaging them.
• Changed: Added MiniMax M2.7 recommendation preferences in src/model/catalog.ts; documented model switching, authenticated-provider visibility, and /feynman-model subagent overrides in website/src/content/docs/getting-started/configuration.md and website/src/content/docs/reference/slash-commands.md; added a runtime patch helper in scripts/lib/pi-google-legacy-schema-patch.mjs and wired scripts/patch-embedded-pi.mjs to normalize JSON Schema const into enum for the legacy parameters field used by Cloud Code Assist Claude models.
• Verified: Ran npm test, npm run typecheck, npm run build, and cd website && npm run build after the patch/helper/docs changes.
• Failed / learned: The MiniMax provider catalog in Pi already uses canonical IDs like MiniMax-M2.7, so the only failure during validation was a test assertion using the wrong casing rather than a runtime bug.
• Blockers: The Cloud Code Assist fix is validated by targeted patch tests and code-path review rather than an end-to-end Google account repro in this environment.
• Next: Push the tracker-triage commit, close the docs/MiniMax PRs as superseded by main, close the support-style model issues against the new docs, and decide whether the remaining feature requests should be left open or closed as not planned/upstream-dependent.