[rorychatt]

What does this PR do?

Adds Ivy Tendril to the Agent Coding and Software Engineering category.

Catalog entry

• Repository: https://github.com/Ivy-Interactive/Ivy-Tendril
• Category: coding
• License: FSL-1.1-ALv2 source-available license. It permits use other than Competing Use; the current restriction covers offering a competing commercial product or service. Each release converts to Apache-2.0 after two years.
• Scope: Coordinates parallel Git worktrees for agentic software engineering with programmatic verification and review workflows.

The entry is defined in data/projects.json and README.md is generated from that source.

[autogame-17]

Reviewed head a72dd6ea19b9b00559f31e58b39813a940fda7bd. Please address the following before inclusion:

1. README.md:193 bypasses the canonical data source. The PR only inserts Ivy Tendril inside AUTOGEN:prompt-optimization; there is no corresponding record in data/projects.json. On an untouched checkout, Node 24.19.0 actually reports:

   Validated 119 projects across 10 categories
   Validation failed with 1 error(s):
   - README is not reproducible from data/projects.json
   

   Running node scripts/generate-readme.js then removes exactly that one line (230 bytes). A subsequent validator pass is green only because the proposed entry has disappeared. Please add a schema-valid JSON record first and regenerate README, as required by CONTRIBUTING. The link checker also reads JSON only, so its result does not cover this README-only URL.
2. The “Open-source” claim does not match the current license. The canonical upstream README explicitly says “source-available”, and its LICENSE is FSL-1.1-ALv2 with a competing-use restriction. Apache-2.0 is a future per-version grant after two years, not the current unrestricted license. Please accurately disclose FSL/source-available status in both the entry and PR body so maintainers can assess inclusion; GitHub's NOASSERTION alone was not used as evidence.
3. The placement does not match the described capability. This change lands in Prompt and Behaviour Optimization, not the Multi-Agent Frameworks section named in the PR title. Upstream documents coding-agent worktrees, code review and verification gates, not prompt optimization. Please justify an appropriate category (coding fits the documented software-engineering workspace); if the primary contribution you want to list is team/swarm orchestration, use the sibling swarm list instead. Use an objective description rather than “an amazing UI”.

The current branch also conflicts with latest upstream main (696251db2101902baf98e78899ca195d3d2c6f42) in README. Refresh from upstream, resolve the JSON/source-of-truth change, and regenerate rather than hand-editing the generated block.

Validate the updated committed content with:

node scripts/generate-readme.js
node scripts/validate.js
git diff --check
node scripts/check-links.js

Separate baseline issue: the full link check returned 118 ok, 1 failure, 0 warnings, with an HTTP 404 for existing Fzkuji/OpenProgram; that is not an Ivy URL failure and is not a request to remove unrelated entries. Ivy's canonical repository itself was accessible, active, documented, and not archived. The current validate workflow is action_required with 0 jobs; it has not executed the validator and must not be treated as passing.

[autogame-17]

Verified the refreshed catalog-only diff against current main. The entry is now source-of-truth JSON in the coding category, uses an objective description, and accurately discloses FSL-1.1-ALv2 source-available terms and the Competing Use restriction. Generated README, validation, and link checks passed locally and in the two current GitHub Actions jobs.