@reicek/neataptic-ts 0.1.26 → 0.1.27

package/plans/asciiMaze-typescript-repair.logs.md

@@ -0,0 +1,35 @@
+# ASCII Maze TypeScript Repair Log
+
+**Status:** [DONE]
+
+## Audit scope
+
+- Objective: clear the remaining `test/examples/asciiMaze/**` TypeScript
+  diagnostics that were intentionally left after the NEAT compatibility repair.
+
+## Durable milestones
+
+### [DONE] Browser-entry compatibility fixes
+
+- Repaired browser-entry typing issues including window casting and broader
+  record-constraint compatibility.
+
+### [DONE] Evolution-engine and maze-surface repair
+
+- Fixed nullability and callback-contract issues in the evolution engine.
+- Restored typed compatibility across maze setup and network-surface handling.
+
+### [DONE] Telemetry and validation closure
+
+- Cleaned up stale telemetry metric/property usage and any missing references.
+- Closed the lane only after `tsconfig.test.json` reached zero diagnostics and
+  the Jest suite still passed.
+
+## Controls and evidence
+
+- Validation used `npx tsc --noEmit -p tsconfig.test.json` and `npm test`.
+
+## Reopen triggers
+
+- New `asciiMaze` diagnostics appear after later example work.
+- Contract drift reappears between the example surface and library types.

package/plans/asciiMaze-typescript-repair.plans.md

@@ -4,39 +4,33 @@
 
 ## Scope
 
-Repair the remaining `test/examples/asciiMaze/**` TypeScript diagnostics in
-`tsconfig.test.json` without disturbing the completed NEAT public-surface fix.
-
-## Current state
-
-- [DONE] Confirmed `npm test` passes from the current repo state.
-- [DONE] Confirmed `npx tsc --noEmit -p tsconfig.test.json` still fails only in `test/examples/asciiMaze/**`.
-- [DONE] Grouped the remaining diagnostics into local compatibility buckets before editing.
-
-## Coverage backlog
-
-- [DONE] Browser-entry type compatibility fixes.
-  Files: `browser-entry/browser-entry.globals.services.ts`, `browser-entry/browser-entry.host.services.ts`.
-  Failure shape: window casting overlap and generic `Record<string, unknown>` constraints.
-- [DONE] Evolution-engine nullability and callback-contract fixes.
-  Files: `evolutionEngine.ts`, `evolutionEngine/neatConfiguration.ts`.
-  Failure shape: `Neat | null` flow, warm-start callback signature mismatch, and constructor overload typing.
-- [DONE] Maze setup and network surface compatibility fixes.
-  Files: `evolutionEngine/optionsAndSetup.ts`, `evolutionEngine/populationPruning.ts`, `asciiMaze.e2e.test.ts`.
-  Failure shape: missing imports, `undefined` maze source handling, and `Network` vs `INetwork` adaptation seams.
-- [DONE] Telemetry metrics cleanup.
-  Files: `evolutionEngine/telemetryMetrics.ts`.
-  Failure shape: stale property names and missing local symbol references.
-- [DONE] Final validation with `npx tsc --noEmit -p tsconfig.test.json` and `npm test`.
-
-## Validation
-
-- `npx tsc --noEmit -p tsconfig.test.json` completed with no diagnostics.
-- `npm test` completed successfully from the current repo state.
-
-## Handoff query
-
-```text
-Continue from the current repo state only. Do not rely on prior chat history.
-Work from plans/asciiMaze-typescript-repair.plans.md. The ASCII Maze TypeScript repair pass is complete: browser-entry, evolution-engine, setup/pruning, and telemetry compatibility seams were aligned, `npx tsc --noEmit -p tsconfig.test.json` is green, and `npm test` passes. Preserve unrelated user changes and only reopen this area if new diagnostics appear.
-```
+- Repair the remaining `test/examples/asciiMaze/**` TypeScript diagnostics from
+  the current repo state.
+- Keep the repair constrained to example compatibility rather than reopening
+  unrelated runtime work.
+
+## Final state
+
+- The `asciiMaze` example lane no longer carries the TypeScript diagnostics that
+  remained after the NEAT public-surface repair work.
+- Browser-entry, evolution-engine, maze setup/network surface, and telemetry
+  compatibility issues were brought back into a stable typed state.
+- No active backlog remains; this file is now a reopen point for future
+  `asciiMaze` diagnostics.
+
+## Audit summary
+
+- Validation used `npx tsc --noEmit -p tsconfig.test.json` and `npm test` from
+  the current repo state.
+- The lane closed only after the remaining example diagnostics reached zero.
+
+## Reopen conditions
+
+- New `asciiMaze` example diagnostics appear in `tsconfig.test.json`.
+- Example-surface nullability or contract drift reappears after later changes.
+- Test-lane API changes require another example compatibility pass.
+
+## Audit log
+
+- Durable completion notes now live in
+  [asciiMaze-typescript-repair.logs.md](asciiMaze-typescript-repair.logs.md).

package/plans/generate-docs-solid-split.logs.md

@@ -0,0 +1,36 @@
+# Generate Docs SOLID Split Log
+
+**Status:** [DONE]
+
+## Audit scope
+
+- Objective: split the docs generator into a folder-owned subsystem without
+  breaking script build or generated docs output.
+
+## Durable milestones
+
+### [DONE] Generator root split
+
+- Broke the flat generator into stable ownership areas for constants, types,
+  state, targets, symbols, ordering, and output behavior.
+
+### [DONE] Direct-path migration
+
+- Retargeted repo callers to the stable generated script path instead of using
+  a compatibility shim or old flat entry expectations.
+
+### [DONE] Regression repair and nested follow-through
+
+- Completed the symbols and output chapter split.
+- Fixed the discovered regressions in intro-file control and folder-index link
+  paths before closing the workstream.
+
+## Controls and evidence
+
+- Validation used `npm run docs:build-scripts` and `npm run docs`.
+- Docs output remained stable at closeout.
+
+## Reopen triggers
+
+- Generator features outgrow the current folder ownership.
+- Output regressions appear in link rewriting or intro selection.

package/plans/generate-docs-solid-split.plans.md

@@ -4,84 +4,32 @@
 
 ## Scope
 
-- Split the docs generator from the old flat [scripts/generate-docs.ts](../scripts/generate-docs/generate-docs.ts) boundary into a folder-owned module under `scripts/`.
-- Keep the `docs:folders:*` CLI behavior stable by updating repo-local callers to the new built entrypoint instead of leaving a flat compatibility shim.
-- Improve source readability with orchestration-first flow, focused helper ownership, and comprehensive JSDoc on the new exported surfaces.
+- Split the docs generator into a stable folder-owned module boundary while
+  keeping `npm run docs` behavior intact.
+- Leave the generator ready for reopen-only follow-up instead of an active
+  refactor frontier.
 
-## Current state
+## Final state
 
-- Split root: `scripts/generate-docs/`
-- Nearest README reviewed: `n/a` (no `scripts/**/README.md` files currently exist)
-- Parent README reviewed: `n/a`
-- Relevant plan: [plans/neat-docs.plans.md](../plans/neat-docs.plans.md)
-- Adjacent reference checked: [plans/architecture-solid-split.plans.md](../plans/architecture-solid-split.plans.md)
-- Current boundary: the root entrypoint now delegates to focused chapter files for targets, symbols, ordering, output, constants, state, and shared contracts.
-- Active split frontier: `generate-docs.symbols.ts` and `generate-docs.output.ts` have each grown into their own responsibility clusters and now need direct-path subfolderization.
+- The docs generator now has a folder-owned structure with clear ownership for
+  constants, types, state, targets, symbols, ordering, and output concerns.
+- Repo callers were moved to the stable generated-script path instead of
+  relying on the pre-split flat layout.
+- No active backlog remains; this file is now a reopen point for later
+  generator-boundary work.
 
-## Durable rules
+## Audit summary
 
-- Keep exactly one active workstream section.
-- Prefer direct-path migration to `scripts/generate-docs/generate-docs.ts`; do not leave a flat shim unless a real compatibility need appears.
-- Do not hand-edit generated README files as part of this split.
-- Run docs-tooling validation after the split because this boundary feeds `npm run docs`.
+- Validation used `npm run docs:build-scripts` and `npm run docs`.
+- Behavioral regressions discovered during the split were fixed before closure.
 
-## Target shape
+## Reopen conditions
 
-- `scripts/generate-docs/generate-docs.ts` owns CLI orchestration.
-- `scripts/generate-docs/generate-docs.types.ts` owns shared docs-generator contracts.
-- `scripts/generate-docs/generate-docs.constants.ts` owns stable constants and target definitions.
-- `scripts/generate-docs/generate-docs.state.ts` owns shared ts-morph and docs-order cache state.
-- `scripts/generate-docs/generate-docs.targets.ts` owns target resolution and source-tree preparation.
-- `scripts/generate-docs/generate-docs.symbols.ts` owns symbol collection, JSDoc extraction, and dedupe rules.
-- `scripts/generate-docs/generate-docs.order.ts` owns `docs.order.json` loading, validation, caching, and warnings.
-- `scripts/generate-docs/generate-docs.output.ts` owns README rendering, folder-index rendering, and file emission.
+- New generator features make the current folder ownership too coarse.
+- Docs-output behavior regresses in intro-file control or generated links.
+- Another nested split becomes necessary in the generator area.
 
-## Coverage backlog
+## Audit log
 
-### [DONE] Generator root split
-
-- Landed the folder-owned module at [scripts/generate-docs/generate-docs.ts](../scripts/generate-docs/generate-docs.ts) with dedicated chapter files for constants, types, state, targets, symbols, ordering, and output.
-- Retargeted the repo-local docs scripts to `dist-docs/scripts/generate-docs/generate-docs.js` so the split uses direct-path migration with no flat compatibility shim.
-- Updated the existing plan references that pointed at the deleted flat script path.
-- Completed the required educational-docs follow-up by adding chapter-level source introductions to the new files so maintainers can read the split as a guided boundary map instead of a raw helper shelf.
-
-### [DONE] Symbols and output chapter split
-
-- Reopen the generator boundary to move `generate-docs.symbols.ts` into `scripts/generate-docs/symbols/` and `generate-docs.output.ts` into `scripts/generate-docs/output/`.
-- Keep direct-path migration: update repo-local imports to the new subfolder entrypoints and delete the flat files after validations pass.
-- Keep the new chapter roots orchestration-first, with narrower helper files for collection/rendering/signature work in the symbols boundary and README/index ordering work in the output boundary.
-- Completed the direct-path move into `scripts/generate-docs/symbols/` and `scripts/generate-docs/output/`, removed the flat chapter files, and retargeted the root generator imports to the new nested entrypoints.
-- Fixed the post-split behavioral regressions in the output boundary so `introFile` once again controls directory intro promotion and folder-index nodes keep correct source and link paths.
-- Completed the mandatory educational-docs follow-up with contract-level JSDoc covering signature storage, file-summary precedence, intro promotion, and fallback ordering.
-
-## Validation
-
-- Completed in prior step:
-  - `npm run docs:build-scripts`
-  - `npm run docs`
-  - `npm run docs:build-scripts` after the educational-docs follow-up
-- Completed for this step:
-  - `npm run docs:build-scripts`
-  - `npm run docs`
-  - `npm run docs:build-scripts` after the post-validation educational-docs follow-up
-
-## Immediate next steps
-
-- No further split work is queued in this boundary right now.
-- Future work, if needed, should start from the nested `symbols/` and `output/` folders rather than recreating flat chapter files.
-
-## Handoff query
-
-```text
-Continue docs-tooling work from the current repo state only. Do not rely on prior chat history.
-
-Plan: plans/generate-docs-solid-split.plans.md
-Current boundary: scripts/generate-docs/
-Repo standard: migrate directly to scripts/generate-docs/generate-docs.ts with no compatibility shim by default, and keep the split in small responsibility chapters.
-Small-chapter standard: this applies to scripts and tooling boundaries too, not only library code.
-Already covered: the old flat generator script was removed, package.json now points at dist-docs/scripts/generate-docs/generate-docs.js, and the current root chapter files own targets, symbols, ordering, output, state, constants, and types.
-Next task if this boundary reopens: continue from the nested scripts/generate-docs/symbols/ and scripts/generate-docs/output/ folders, preserving direct-path imports and the current docs-order behavior.
-Required validations: npm run docs:build-scripts, npm run docs.
-Worktree caution: .github/copilot-instructions.md may already have unrelated local edits.
-Continue from the current repo state only. Do not rely on prior chat history.
-```
+- Durable completion notes now live in
+  [generate-docs-solid-split.logs.md](generate-docs-solid-split.logs.md).

package/plans/methods-docs.logs.md

@@ -0,0 +1,37 @@
+# Methods Docs Plan Log
+
+**Status:** [DONE]
+
+## Audit scope
+
+- Objective: turn the root-facing `src/methods/` chapters into educational
+  introductions that explain the policy choices behind each family.
+
+## Durable milestones
+
+### [DONE] Root methods chapter framing
+
+- Strengthened the root methods chapter so it introduces the family map and the
+  role each method family plays in the library.
+
+### [DONE] Family-level educational reframing
+
+- Reframed activation around transfer-curve choice, gating around placement
+  semantics, and connection around wiring policy so the generated openings
+  answer reader questions instead of just listing exports.
+
+### [DONE] Polish follow-through
+
+- Completed the root alignment and rate/mutation polish passes needed to make
+  the whole methods lane read consistently.
+
+## Controls and evidence
+
+- Documentation updates were validated with `npm run docs` and
+  `npx tsc --noEmit -p tsconfig.json`.
+- No runtime behavior changes were required for this pass.
+
+## Reopen triggers
+
+- Methods chapter openings drift back toward shelf-like generated output.
+- A new family or reordered source owner needs a documentation refresh.

package/plans/methods-docs.plans.md

@@ -4,194 +4,33 @@
 
 ## Scope
 
-This plan tracks educational-docs passes for the shared method vocabulary under
-[src/methods/README.md](../src/methods/README.md).
+- Educational-docs pass for the shared vocabulary and chapter openings under
+  `src/methods/`.
+- Improve the generated first-contact reading path without changing runtime
+  behavior.
 
-Primary reader:
+## Final state
 
-- readers who want the reusable training and evolutionary method families to
-  read like a guided policy shelf rather than a raw export list.
+- The methods root and the key family chapters now open with clearer
+  educational framing around what choices the families represent.
+- Activation, gating, connection, rate, and mutation documentation now better
+  answer the reader's boundary-level questions instead of acting like symbol
+  shelves.
+- No active backlog remains; this plan is now a reopen point for documentation
+  drift in `src/methods/`.
 
-Primary surfaces:
+## Audit summary
 
-- [src/methods/methods.ts](../src/methods/methods.ts)
-- [src/methods/cost/cost.ts](../src/methods/cost/cost.ts)
-- [src/methods/rate/rate.ts](../src/methods/rate/rate.ts)
-- [src/methods/selection/selection.ts](../src/methods/selection/selection.ts)
-- [src/methods/gating/gating.ts](../src/methods/gating/gating.ts)
-- [src/methods/connection/connection.ts](../src/methods/connection/connection.ts)
-- [src/methods/README.md](../src/methods/README.md)
+- Documentation-affecting passes regenerated docs with `npm run docs`.
+- Type safety was preserved with `npx tsc --noEmit -p tsconfig.json`.
 
-## Session Log
+## Reopen conditions
 
-### Methods root chapter pass
+- A methods chapter opening regresses below the current educational-docs bar.
+- A new methods family needs the same chapter-framing treatment.
+- Generator ordering causes a methods README to open from the wrong owner.
 
-Goals:
+## Audit log
 
-- Make the generated [src/methods/README.md](../src/methods/README.md) open as
-  a guided chapter instead of a raw export list.
-
-Progress:
-
-- Added a barrel-led introduction in
-  [src/methods/methods.ts](../src/methods/methods.ts) so the chapter now opens
-  with the shared method-family map.
-- Added [src/methods/docs.order.json](../src/methods/docs.order.json) to keep
-  `methods.ts` as the intro source and hide the barrel file section.
-- Strengthened the cost, rate, and selection family surfaces with clearer
-  framing and diagram-justified guidance.
-
-Decision:
-
-- Keep future methods work proportional and continue one family chapter at a
-  time rather than reopening the entire folder.
-
-### Activation chapter pass
-
-Goals:
-
-- Make the activation family read more like a chooser and less like a flat
-  list of transfer-curve helpers.
-- Tighten the older symbol-level prose in the utility shelf without changing
-  runtime behavior.
-
-Progress:
-
-- Added a compact family map in
-  [src/methods/activation/activation.ts](../src/methods/activation/activation.ts)
-  so the generated activation chapter shows the main activation clusters before
-  readers fall into the long symbol shelf.
-- Strengthened
-  [src/methods/activation/activation.utils.ts](../src/methods/activation/activation.utils.ts)
-  with a clearer reading order and more explanatory JSDoc for the previously
-  terse helper functions, especially the historical, localized, and niche
-  transforms.
-
-Decision:
-
-- Leave the deeper per-symbol registry cleanup for a later polish pass and keep
-  moving through the thin structural chapters one family at a time.
-
-### Gating chapter pass
-
-Goals:
-
-- Make the gating family read like a structural chooser instead of a short
-  constant shelf.
-- Clarify how `INPUT`, `OUTPUT`, and `SELF` differ so readers can pick a gate
-  position by intent instead of memorizing names.
-
-Progress:
-
-- Reframed [src/methods/gating/gating.ts](../src/methods/gating/gating.ts)
-  around the placement question the family answers, with stronger source-first
-  chooser guidance for the three gate positions.
-- Tightened each gate entry so the generated chapter explains the control
-  surface each option creates and includes a minimal example for quick recall.
-
-Remaining gaps:
-
-- The sibling structural family for connection policies is still thinner than
-  the rest of the methods shelf and likely needs the same chapter-first framing.
-- If the methods root chapter gets another pass later, its short gating summary
-  can be aligned again with any wording refinements that come out of the
-  connection pass.
-
-Next step:
-
-- Move to the connection family next and give its structural wiring vocabulary
-  the same chooser-first treatment used for gating.
-
-### Connection chapter pass
-
-Goals:
-
-- Make the connection family read like a wiring-policy chooser instead of a
-  terse list of topology names.
-- Clarify when dense connectivity, dense-without-self-links, and one-to-one
-  alignment are the right structural defaults.
-
-Progress:
-
-- Reframed [src/methods/connection/connection.ts](../src/methods/connection/connection.ts)
-  around the structural question the family answers, with stronger source-first
-  guidance for the three built-in wiring patterns.
-- Tightened each connection policy entry so the generated chapter explains the
-  wiring bias each option introduces and includes a minimal example for quick
-  recall.
-
-Remaining gaps:
-
-- The thin structural families are now better aligned, so future work here is
-  more likely to be polish than rescue.
-- If the methods root chapter gets another pass later, its short structural
-  summaries for both gating and connection can be harmonized again for tone.
-
-Next step:
-
-- Re-read the methods root chapter and decide whether the next highest-value
-  pass is a small root-summary alignment pass or a deeper polish pass on one of
-  the larger method families.
-
-### Methods root alignment pass
-
-Goals:
-
-- Re-align the root methods introduction so its structural summary matches the
-  stronger gating and connection chapters.
-- Keep the top-level chapter compact while making the difference between
-  routing control and wiring layout explicit.
-
-Progress:
-
-- Tightened [src/methods/methods.ts](../src/methods/methods.ts) so the root
-  chapter now describes `gating` and `groupConnection` as different parts of
-  the structural vocabulary instead of bundling them together too loosely.
-- Cleaned the duplicated top-level module JSDoc in
-  [src/methods/methods.ts](../src/methods/methods.ts) so the generated root
-  opening stays compact and source-first.
-
-Remaining gaps:
-
-- The methods root is now aligned with the thin structural chapters, so the
-  next useful pass is more likely to be selective polish than root framing.
-- Larger families such as mutation or rate may still benefit from later
-  refinement, but they no longer block the root chapter from reading clearly.
-
-Next step:
-
-- Choose the next highest-value polish pass among the larger method families,
-  or stop here if the methods shelf is sufficiently aligned for now.
-
-### Rate and mutation polish pass
-
-Goals:
-
-- Smooth the generated docs for two larger method-adjacent chapters without
-  reopening their runtime behavior.
-- Remove remaining generated-doc rough edges such as duplicated framing and
-  awkward parameter prose.
-
-Progress:
-
-- Tightened [src/methods/rate/rate.ts](../src/methods/rate/rate.ts) so the
-  class-level chapter no longer repeats the full module opening and instead
-  acts like a practical chooser for schedule builders.
-- Filled the missing return and option guidance for the reactive and warm
-  restart rate helpers in
-  [src/methods/rate/rate.ts](../src/methods/rate/rate.ts) so the generated API
-  shelf reads more evenly.
-- Polished [src/neat/mutation/mutation.ts](../src/neat/mutation/mutation.ts)
-  with a clearer root reading order and cleaner parameter descriptions so the
-  generated mutation chapter reads less like raw annotation output.
-
-Decision:
-
-- Stop the methods documentation lane here for now; the root and the highest-
-  leverage family chapters now read coherently enough that further work is
-  polish, not structural rescue.
-
-Next step:
-
-- Pause this plan and revisit only if a later docs pass exposes a specific
-  regression, stale generated wording, or a newly expanded method family.
+- Durable completion notes now live in
+  [methods-docs.logs.md](methods-docs.logs.md).

package/plans/methods-solid-split.logs.md

@@ -0,0 +1,41 @@
+# methods SOLID Split Log
+
+**Status:** [DONE]
+
+## Audit scope
+
+- Objective: move `src/methods/` from a flat collection of families into a
+  folder-owned module structure with durable README chapter ownership.
+
+## Durable milestones
+
+### [DONE] Family folderization
+
+- Folderized the activation, cost, rate, selection, mutation, crossover,
+  gating, and connection families into stable chapter boundaries.
+- Removed the need to keep the mutation family as a flat special case.
+
+### [DONE] Import-path migration
+
+- Retargeted repo-local imports to the new folder structure instead of relying
+  on transitional flat-file ownership.
+- Preserved public behavior while simplifying future maintenance in the methods
+  area.
+
+### [DONE] Documentation ownership follow-through
+
+- Added root and local `docs.order.json` controls so the generated methods root
+  reads as a chapter map rather than a flat symbol shelf.
+- Closed the documentation follow-through exposed by the structural split.
+
+## Controls and evidence
+
+- Validation after split work used `npm run docs` and
+  `npx tsc --noEmit -p tsconfig.json`.
+- The final methods structure is now the baseline for future reopen-only work.
+
+## Reopen triggers
+
+- A method family becomes oversized again.
+- Import-path drift or README ownership regressions appear after later work.
+- Additional family-level splits become necessary.

package/plans/methods-solid-split.plans.md

@@ -2,77 +2,35 @@
 
 **Status:** [DONE]
 
-## Purpose
+## Scope
 
-Reduce the overloaded flat `src/methods/` surface into small chapter folders so
-the generated methods README stops behaving like one monolithic page. Keep
-`src/methods/methods.ts` as the orchestration-first public facade while moving
-each concept into its own folder-based boundary.
+- Replace the flat `src/methods/` layout with folder-owned chapter boundaries
+  for the main method families.
+- Keep the generated methods root readable and ownership-oriented after the
+  split.
 
-## Root
+## Final state
 
-- Split root: `src/methods`
-- Nearest README reviewed: `src/methods/README.md`
-- Parent README reviewed: `src/README.md`
-- Relevant plan: `n/a`
+- The major method families are now folderized and imported through stable
+  chapter boundaries instead of the previous flat-file cluster.
+- Root and local `docs.order.json` controls keep generated README openings tied
+  to the correct public chapter maps.
+- No active backlog remains; this plan is now the reopen point for later method
+  family expansion or new oversized-boundary work.
 
-## Durable Rules
+## Audit summary
 
-- Keep exactly one active step at a time.
-- Update this plan immediately after each completed step.
-- Use direct-path migration for repo-local imports; do not leave flat shim files.
-- Do not hand-edit generated README files; improve source JSDoc and run docs.
-- Keep `src/methods/methods.ts` as the readable public facade.
+- Structural and documentation follow-through were validated with
+  `npm run docs` and `npx tsc --noEmit -p tsconfig.json`.
+- The methods root no longer acts as a monolithic blocker for modernization.
 
-## Target Shape
+## Reopen conditions
 
-- `src/methods/methods.ts` remains the public facade.
-- `src/methods/activation/` owns activation registry and utility math helpers.
-- `src/methods/cost/` owns cost facade and cost utility helpers.
-- `src/methods/rate/` owns schedule facade and rate utility helpers.
-- `src/methods/selection/`, `src/methods/mutation/`, `src/methods/crossover/`,
-  `src/methods/gating/`, and `src/methods/connection/` each become small chapter folders.
-- Root docs ordering should describe chapter folders instead of a flat file list.
+- Another method family grows beyond the current folder structure.
+- Import paths or generated chapter ownership drift after later refactors.
+- The methods root README needs another chapter-map correction.
 
-## Steps
+## Audit log
 
-- [x] Step 1: Folderize the methods categories, migrate repo-local imports to the new direct paths, and keep the root facade stable.
-- [x] Step 2: Refresh generated docs ordering and educational-docs policy so oversized folder READMEs are split proactively.
-- [x] Step 3: Validate the split surface and record the handoff state.
-
-## Latest Pass
-
-- Folderized the methods surface into chapter folders for `activation`, `cost`,
-  `rate`, `selection`, `mutation`, `crossover`, `gating`, and `connection`.
-- Migrated repo-local imports to direct folder paths and removed the stale flat
-  `src/methods/mutation.ts` file that was still being compiled after the move.
-- Updated `src/methods/methods.ts` to remain the root public facade and updated
-  root ordering via `src/methods/docs.order.json`.
-- Added chapter-level ordering configs for `activation`, `cost`, and `rate` so
-  their nested READMEs open from the public facade files rather than utility
-  helpers.
-- Updated `.github/skills/educational-docs/SKILL.md` so oversized generated
-  folder READMEs now point toward `solid-split` instead of continuing to grow
-  monolithically.
-- Regenerated docs and verified the generated openings for
-  `src/methods/README.md`, `src/methods/activation/README.md`,
-  `src/methods/cost/README.md`, and `src/methods/rate/README.md`.
-- Final validation completed with `npm run docs` and
-  `npx tsc --noEmit -p tsconfig.json`.
-
-## Handoff State
-
-- The split is complete and the root methods README now reads as a chapter map
-  rather than a monolithic flat file dump.
-- Nested method READMEs are generated from source-first JSDoc and should be
-  maintained by editing the owning source files, not the generated READMEs.
-- If a future methods family starts to feel oversized again, prefer another
-  bounded folder split over expanding the root README.
-
-## Done Criteria
-
-- The flat `src/methods/*.ts` category files have been replaced by chapter folders.
-- Repo-local imports point at the new direct folder paths.
-- `src/methods/README.md` becomes smaller because chapter content moves into nested folder READMEs.
-- The educational-docs skill explicitly points large monolithic README surfaces toward `solid-split`.
-- The boundary can be resumed safely from this plan alone.
+- Durable completion notes now live in
+  [methods-solid-split.logs.md](methods-solid-split.logs.md).