Update fpm.toml to link fortfront static library

[krystophny]

Status: fmp Dependency Management Already Complete

The fmp.toml is already correctly configured with fortfront dependency. fmp automatically handles all build complexity.

Current Configuration (No Changes Needed)

# fmp.toml (CURRENT STATE)
[dependencies]
fortfront = { path = "../fortfront" }
stdlib = "*"

What fmp Automatically Provides

• Automatic Dependency Resolution: fmp resolves fortfront from local path
• Static Linking: fmp handles all linking automatically
• Build Management: Single fpm build command produces static executable
• Zero Configuration: No manual build setup required

Misconception Corrected

This issue was based on the incorrect assumption that manual static linking configuration was needed. fpm's dependency management system handles this automatically when fortfront is listed in dependencies.

Verification That It Works

# Current build works with zero configuration
fpm build           # Builds fluff with fortfront automatically linked
fpm test            # Runs tests with fortfront integration

Required Actions

1. Update documentation to reflect fpm's automatic dependency management
2. Remove references to manual linking complexity from roadmap
3. Focus on API usage patterns rather than build configuration

Definition of Done

• fmp.toml already has fortfront dependency configured
• Build system automatically handles static linking
• Documentation updated to reflect fmp's capabilities
• Remove manual linking references from other issues
• Update roadmap to focus on API rather than build complexity

Dependencies

• Still requires Wait for fortfront static library foundation before proceeding #66 (fortfront API stabilization), but NOT for build reasons
• Build architecture is already complete via fmp dependency management

Notes

This clarifies that fmp elegantly handles the fortfront dependency automatically. No manual build configuration is needed - this significantly simplifies the development workflow.