Release: Safer Automation And Dogfood Validation

Forgeflow 4.3.10 closes the latest automation sprint with safer command routing, stronger project-learning hygiene, topology-guided review focus, and a packaged dogfood self-test.

Automation Safety

• Command wrappers now have regression coverage for safer argument handling and quoting across Forgeflow command docs.
• Release-version checks reject symlinked or off-repo manifest, command, doc, and changelog targets before reading them.
• Source smoke no longer falls back to the installed helper repo when a requested source tree lacks source tests.

Review And Learning

• Code topology now carries topology-guided review focus into changed-file neighborhoods and context-pack summaries.
• Project-learning candidates support active, stale, and superseded lifecycle metadata, with inactive candidates omitted from agent-facing guidance.
• Learning quality checks now warn on missing freshness metadata and block private URL forms including SSH and Git shorthand.
• Adoption next actions now include clearer owner, blocker, fix-layer, command, and reason fields.

Dogfood And Release Confidence

• test-dogfood-self-test.js exercises a disposable Git project through health repair, learning record and rollup, context-pack injection, code map, trends, report, and downstream smoke.
• smoke-check.js --mode source --json now includes the dogfood self-test as a packaged source-tree release guard.
• Release docs explain why the dogfood test is listed directly and also included in source smoke.

Validation

• Full local release-gate validation passed before tagging.
• Source-mode smoke passed with command coverage, docs links, plugin manifest, release-version, install-manifest, update, and dogfood self-test checks.
• Forgeflow review approved the automation, lifecycle, topology, and dogfood slices after safety and wording fixes.