Release: Learning Signals, Support Bundles, And Cross-Project Topology

Forgeflow 4.3.16 turns review outcomes into practical planning guidance, adds a local support bundle for maintainers, strengthens implementation handoffs, and improves code topology across monorepos and mixed-language projects.

Project Learning Loop

• build-project-intelligence.js now consumes aggregate review-outcome signals without exposing raw local records.
• Next-work guidance and review-prep notes can account for confirmed noise, missed issues, stale guidance, and manual promotion candidates.
• Learning-driven candidates are priority sorted before the five-item cap so current high-risk work stays visible.

Local Support And Contracts

• /forgeflow-support creates a local JSON and Markdown support bundle with version, health, smoke, release-readiness, docs-drift, trend, and next-action context.
• Support bundles keep source-only checks gated to the Forgeflow checkout and avoid executing arbitrary project-local validators.
• test-artifact-contracts.js guards representative local JSON contracts for project intelligence, review outcomes, release readiness, and version support snapshots.

Implementation Handoffs

• build-project-intelligence.js --brief <index> now renders suggested review lanes, implementation-notes seed prompts, and a handoff checklist.
• The brief remains advisory and keeps product intent confirmation, validation, and review approval explicit.

Code Topology

• Static topology now resolves local package.json imports aliases such as #shared/*.
• Package aliases are scoped to the nearest package root so aliases do not leak across packages or into nested workspaces.
• External or path-traversing package import targets remain external instead of becoming unsafe local graph edges.
• Topology and code-map output now show unsupported-language scope for common non-JS/TS source files.

Validation

• Focused tests, full scripts/forgeflow/test-*.js, docs checks, and Forgeflow reviews passed across all five phases.
• Review fixes covered candidate priority ordering, artifact contract coverage, support-bundle source gating, advisory handoff wording, package alias scoping, and traversal-safe package import targets.