mirror of
https://github.com/hanzoai/swift-sdk.git
synced 2026-10-30 18:20:19 +00:00
zeekay
b0db427c79
The projection was 113 commits behind the document it claims to describe, and `generate.py --all --check` reported every one of the thirteen clients DRIFTED — the same +19 models in each, because they all fell behind the same emission. Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4 (sha256 087024f6…), which is the only description of this API that cannot name a route the binary does not serve. `--check` is clean across all thirteen after. .spec-lock moved with the code. The generator READS that file and never writes it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous document. A lock that disagrees with the tree beside it is worse than no lock: the next `--check` without `--spec` fetches what production serves, compares it to a digest that was already wrong, and reports drift that is really staleness.
36 lines
994 B
Swift
36 lines
994 B
Swift
//
|
|
// AiMCPApp.swift
|
|
//
|
|
// Generated by openapi-generator
|
|
// https://openapi-generator.tech
|
|
//
|
|
|
|
import Foundation
|
|
|
|
public struct AiMCPApp: Sendable, Codable, ParameterConvertible, Hashable {
|
|
|
|
/** Name is the subsystem, as the manifest names it. */
|
|
public var name: String?
|
|
/** Served reports that THIS process mounted it, so its tools are on this process's MCP server rather than behind a sibling this process only knows the name of. */
|
|
public var served: Bool?
|
|
|
|
public init(name: String? = nil, served: Bool? = nil) {
|
|
self.name = name
|
|
self.served = served
|
|
}
|
|
|
|
public enum CodingKeys: String, CodingKey, CaseIterable {
|
|
case name
|
|
case served
|
|
}
|
|
|
|
// Encodable protocol methods
|
|
|
|
public func encode(to encoder: Encoder) throws {
|
|
var container = encoder.container(keyedBy: CodingKeys.self)
|
|
try container.encodeIfPresent(name, forKey: .name)
|
|
try container.encodeIfPresent(served, forKey: .served)
|
|
}
|
|
}
|
|
|