/**
 * Reading and rewriting a module's `telo.yaml` on the way to the artifact.
 *
 * These three transforms sit between the author's manifest and the published
 * one, and both gates that care about the published bytes — `telo publish` and
 * `telo release` — go through them. They were inside the publish command, which
 * is where a second copy would have appeared the moment anything else needed to
 * know what a module ships.
 */
/**
 * Resolve `include:` globs and inline each partial as an extra document, then
 * drop the `include:` key.
 *
 * The declaring file does not exist in the artifact, which is why every
 * module-relative path in a manifest is module-ROOT-relative rather than
 * relative to the file it was written in.
 */
export declare function expandAndInlineIncludes(content: string, manifestDir: string): string;
/** The owner doc's `files:` globs — the payload set the manifest cannot
 *  otherwise name. Empty when none are declared. */
export declare function readFilesPatterns(content: string): string[];
/** The owner doc's `assets:` globs — the author-claimed subset of `files:` that
 *  ships in the lazily materialized asset layer. */
export declare function readAssetPatterns(content: string): string[];
/** The owner doc's `metadata.version` — the tag this artifact publishes under,
 *  and so the version every drift check compares against. */
export declare function readOwnerVersion(content: string): string | undefined;
//# sourceMappingURL=manifest-text.d.ts.map