Use official Links Notation parser for .lino files

[konard]

Summary

Implements issue #7 by integrating the official links-notation npm package to parse .lino (Links Notation) files, replacing the custom hand-written parser.

Changes Made

1. Installed Official Parser

• Added links-notation (v0.11.2) as a dependency
• This is the official JavaScript parser from https://github.com/link-foundation/links-notation

2. Refactored Parser Implementation

File: website/src/utils/linoParser.js

• Uses official parser: Replaced custom line-by-line parsing logic with the official Parser class from links-notation
• Interpreter layer: Created interpretation functions to convert the parsed Link objects into our JSON model structure:
  • extractFieldPath() - Extracts field paths from nested link structures
  • getDeepestValue() - Retrieves values from link chains
  • interpretLinks() - Main interpreter that maps Links to JSON model format
  • extractCapabilitiesFromContent() - Hybrid parser for capabilities field to handle multi-word items

The implementation follows a two-step approach:

1. Parse the .lino content using the official parser
2. Interpret the resulting Links into our application's JSON structure

3. Updated Tests

File: website/src/utils/linoParser.test.js

• Fixed test case with invalid formatting (missing indentation)
• All 13 parser tests passing ✅
• Validates parsing of: model name, dates, weights, capabilities, modalities, limits, and costs

4. Added Experiment Scripts

Created validation scripts in experiments/ folder to understand parser behavior:

• test-parser-experiment.js - Tests basic parsing with sample files
• test-interpreter-experiment.js - Develops and validates interpretation logic
• test-capabilities-experiment.js - Investigates capabilities parsing edge cases

Testing

Unit Tests

✅ All 35 tests passing (35/35)
   - Parser tests: 13/13 ✅
   - Component tests: 12/12 ✅
   - App tests: 10/10 ✅

Build & Lint

✅ Build successful
✅ ESLint passing (no errors)

CI Status

All PR checks are configured to run:

• Lint check
• Unit tests
• Production build

Implementation Notes

Multi-word Capabilities Handling

The Links Notation parser treats space-separated items on the same line as individual tokens. For capabilities like "tool calls" on a single line, we use a hybrid approach:

• Parse overall structure with official parser
• Extract capabilities line-by-line from original content
• This preserves multi-word capability names correctly

Backward Compatibility

The JSON output structure remains identical to the original parser, ensuring no breaking changes for React components consuming the model data.

Related

Fixes #7

🤖 Generated with Claude Code

[konard]

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

📎 Log file uploaded as GitHub Gist (399KB)
🔗 View complete solution draft log

---

Now working session is ended, feel free to review and add any feedback on the solution draft.