v1.0.0-beta1 — Ketch

Naftiko Fleet v1.0.0-beta1 Community Edition — "Ketch" ⚓ — Release Notes

⚓ A ketch is a sturdy two-masted vessel built for longer voyages — and the Fleet's
first Beta is exactly that: the entire Fleet is now confident enough to leave the alpha
harbour together. Beta1 ships Ikanos binary-content support end-to-end, externalises the
full Skipper GitOps resource library into the Fleet, bundles Polychro in the Crafter VSIX,
and extends the Warden skeleton with production-ready deploy manifests and TechDocs. The
platform is now stable enough for real deployments.

What is the Naftiko Fleet?

The Naftiko Fleet is the Community Edition product for
Spec-Driven Integration.
It bundles the tools, documentation, and services needed to design, create, deploy, and
manage a system of Naftiko capabilities — including the Ikanos framework, a VS Code
extension, Backstage templates, a Kubernetes operator, and a documentation & web portal.

A fleet is what you call a group of ships sailing together — here, a group of
capabilities running and governed as one.

This v1.0.0-beta1 release coordinates the promotion of the entire platform from alpha to
beta: Ikanos, Polychro, Crafter, Warden, Skipper, and Shipyard all move together.

✨ Highlights

Ikanos Framework v1.0.0-beta1

The open-source foundation ships its first beta — see the
full Ikanos release notes.

Key updates:

• Binary Content end-to-end — capabilities can now declare, serve, and document binary
  outputs natively across all adapters: new schema fields (mimeType, encoding,
  maxBinarySize), engine runtime core, REST first-class binary outputs, and MCP
  BlobResourceContents for tool results and resources
• Native CLI fully fixed — GraalVM reflect-config.json is complete for serve
  (Restlet/Jetty) and validate (MaxLengthValidator); all alpha4 ClassNotFoundException
  / NoSuchMethodException regressions resolved (#581, #594)
• CI/CD — Dependabot enabled, Slack notifications on nightly failures, OTel null-safety
  annotations
• Version-sync — remaining hardcoded spec versions removed; sync-ikanos-version.py
  extended with additional search paths

Naftiko Skipper — GitOps Resources Externalised

The most visible structural change of beta1: the Skipper public GitOps resources are now
part of the Fleet repository, making them directly consumable without depending on the
operator's private Helm chart.

The following resource sets are now tracked in skipper/:

• ArgoCD Applications (skipper/argocd/) — crds-application.yaml,
  defaults-application.yaml, operator-application.yaml — ready-to-apply ArgoCD
  Application manifests for the full Skipper stack
• ApplicationSet template (skipper/capabilities/applicationset.template.yaml) — the
  Fleet-wide ApplicationSet template for auto-deploying capabilities
• CRDs (skipper/crds/) — naftiko-capability-crd.yaml and
  capability-class-crd.yaml — the full Custom Resource Definition manifests
• Default CapabilityClasses (skipper/defaults/) — dev, standard, and premium
  class definitions ready for cluster import
• Observability dashboards (skipper/observability/dashboards/) — Ikanos Grafana
  dashboard, Datadog dashboard JSON, and Datadog Helm values

Naftiko Crafter — Polychro Bundled in the VSIX

The Crafter publish pipeline now bundles Polychro directly in the VSIX artifact:

• Polychro version and build date are set at publish time and embedded in the extension
  metadata (1a79dd4)
• The publish-naftiko-crafter-assets workflow fetches the Polychro native binaries from
  the latest release or a specific action run — no manual copy step required
  (0e4eb0d)

This closes a long-standing limitation: alpha4 still shipped Crafter with a bundled Spectral
for linting; beta1 is the first release where the VSIX carries the Polychro binary.

Naftiko Warden — Production-Ready Skeleton

The Backstage capability skeleton is now aligned with beta1 and extended with
production-ready manifests:

• ConfigMap — deploy/configmap.yaml added to the skeleton so every scaffolded
  capability ships with a Kubernetes ConfigMap ready for Skipper
• Deployment manifest extended with beta1-aligned fields
• MkDocs — mkdocs.yml added to the skeleton for TechDocs auto-generation
• Backstage catalog split — catalog-info.yaml reorganised into
  backstage/service/catalog-info.yaml and backstage/provided-apis/catalog-info.yaml
  for cleaner API ownership declaration
• Capability template (warden/templates/capability.yml) and the Ikanos skeleton
  updated to the beta1 spec version

CI/CD Automation

• Crafter publish pipeline extended to fetch and embed Polychro binaries automatically
• Warden publish pipeline fixed and simplified
  (c731b9c)
• Warden templates auto-synced from the Warden repository on each release

Documentation

• Fleet README refreshed for alpha4 (Playground links, reader personas, product
  descriptions) (5869467)
• README and EULA updated to reflect the beta1 milestone
• Shipyard documentation updated across all product sites for v1.0.0-beta1

⚠️ Known Limitations

• Naftiko Crafter — Polychro-based linting is now bundled, but deep IDE integration
  (inline diagnostics, quick fixes) remains in progress
• Naftiko Skipper — production hardening continues; ArgoCD ApplicationSet integration
  is now tracked in the Fleet repository and ready for early adopters
• Naftiko Polychro — JaCoCo coverage check on polychro-rulesets is a pre-existing
  gap; fix planned for an upcoming release

🔢 By the Numbers

• 9 commits merged since v1.0.0-alpha4
• 23 files changed, +1,503 / −73 lines
• 4 contributors

🙏 Contributors

• @farah-t-trigui — Skipper GitOps externalisation, CI/CD
• @jlouvel — Framework, README & documentation
• @jeremnaf — Crafter publish pipeline, Warden templates, Skipper, release coordination
• @eskenazit — Framework (native CLI fixes, version-sync hardening)

Full Changelog: v1.0.0-alpha4...v1.0.0-beta1