swink-agent 0.8.0

Core scaffolding for running LLM-powered agentic loops
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132

#![cfg(not(feature = "builtin-tools"))]

//! Regression test for issue #205: `--no-default-features` must not re-enable
//! `builtin-tools` or `transfer` through dev-dependency feature unification.
//!
//! This file only compiles in the dedicated no-default-features regression run.
//! That keeps default-feature workspace test commands from evaluating the
//! assertions under the wrong configuration while still catching feature leaks
//! in the intended command immediately.

/// When `builtin-tools` is genuinely disabled, `BashTool` must not exist.
#[cfg(not(feature = "builtin-tools"))]
#[test]
fn builtin_tools_feature_is_off() {
    // If this file compiles, the feature is truly absent.
    // A leaking dev-dep would re-enable it, making this test vanish from the
    // `--no-default-features` run and the companion assertion below fire instead.
}

/// Safety net: if `builtin-tools` IS enabled during a `--no-default-features`
/// test run, something is leaking features.
#[cfg(feature = "builtin-tools")]
#[test]
fn builtin_tools_must_not_leak_into_no_default_features() {
    panic!(
        "builtin-tools feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

#[cfg(not(feature = "transfer"))]
#[test]
fn transfer_feature_is_off() {}

#[cfg(feature = "transfer")]
#[test]
fn transfer_must_not_leak_into_no_default_features() {
    panic!(
        "transfer feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- artifact-store ---

#[cfg(not(feature = "artifact-store"))]
#[test]
fn artifact_store_feature_is_off() {}

#[cfg(feature = "artifact-store")]
#[test]
fn artifact_store_must_not_leak_into_no_default_features() {
    panic!(
        "artifact-store feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- artifact-tools ---

#[cfg(not(feature = "artifact-tools"))]
#[test]
fn artifact_tools_feature_is_off() {}

#[cfg(feature = "artifact-tools")]
#[test]
fn artifact_tools_must_not_leak_into_no_default_features() {
    panic!(
        "artifact-tools feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- hot-reload ---

#[cfg(not(feature = "hot-reload"))]
#[test]
fn hot_reload_feature_is_off() {}

#[cfg(feature = "hot-reload")]
#[test]
fn hot_reload_must_not_leak_into_no_default_features() {
    panic!(
        "hot-reload feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- tiktoken ---

#[cfg(not(feature = "tiktoken"))]
#[test]
fn tiktoken_feature_is_off() {}

#[cfg(feature = "tiktoken")]
#[test]
fn tiktoken_must_not_leak_into_no_default_features() {
    panic!(
        "tiktoken feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- plugins ---

#[cfg(not(feature = "plugins"))]
#[test]
fn plugins_feature_is_off() {}

#[cfg(feature = "plugins")]
#[test]
fn plugins_must_not_leak_into_no_default_features() {
    panic!(
        "plugins feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}

// --- otel ---

#[cfg(not(feature = "otel"))]
#[test]
fn otel_feature_is_off() {}

#[cfg(feature = "otel")]
#[test]
fn otel_must_not_leak_into_no_default_features() {
    panic!(
        "otel feature is enabled but should not be. \
         A dev-dependency is likely leaking features via Cargo unification."
    );
}