Repository navigation
Roadmap
The repository roadmap tracks current and future work. 0.1.3 is the release baseline; 0.1.4 development implements the initial catalog contract and native C++ validator. Selective asset reads remain planned.
0.1.3 implements native metadata-only reads and bundled core/CLI installation. Its metadata API reads the header and YLSpec frame, without scanning the TOC or loading payload resources. All thirteen core and SDK/package CI jobs passed for that implementation.
P1 now has an authoring schema and native C++ validator, with shared positive/negative vectors. It checks declarations without file I/O. All thirteen core/SDK CI jobs passed for the foundation; see the test report. Auto-detection, locator generation, discovery handles and asset reads remain planned.
A planned optional catalog will describe:
- Icon and README.
- License files and companion terms.
- Contributing guide and security policy.
- Code of conduct, changelog and notices.
Packaging will detect conventional files inside a bounded project root, with explicit overrides. Metadata will contain only presence declarations, formats, package paths, byte locations, lengths and hashes. The file bytes will remain ordinary resources outside metadata.
A separate proposed discovery handle will list descriptors without loading files. An explicit asset request will read only the chosen range and verify its hash, without constructing a Package or scanning TOC, unrelated payloads or signatures. The host will decide when to load each document or icon for its front page.
Read the architecture proposal for the schema, automatic detection policy, integer-offset planning, range I/O, limits and compatibility. A feasibility experiment with the current native writer reached stable addresses in three rounds and read a README using 2001 bytes of a 12340-byte fixture, including metadata, without reading its TOC or other assets.
That experiment is evidence for the design, not a released asset API. The candidate next milestone is 0.1.4, after catalog, writer, native API, all bindings and installed-package tests pass. Later milestones consider localized content, declared README images and a separate authenticated-discovery design.
Checksums do not authenticate a publisher. The current whole-prefix signature still requires a complete signed-prefix read for verification. Markdown rendering and image decoding remain host concerns.
No new presentation command or SDK method in this proposal is implemented in the current 0.1.3 runtime. The roadmap is the delivery source of truth.
YLPlugin · Repository · Releases · Issues · Support · LGPLv3 · Maintained by Cavanshirpro.
Release guide 0.1.3; source development 0.1.4; later features are tracked in the roadmap. Normative contracts: container and profile.