pi-career 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,122 @@
1
+ # Release process
2
+
3
+ This document records the bounded `v0.1.0` release process and evidence requirements.
4
+
5
+ ## Approved channel boundary
6
+
7
+ After every gate below is closed, the authorized channels are:
8
+
9
+ 1. one public `pi-career@0.1.0` npm package;
10
+ 2. one annotated, unsigned `v0.1.0` Git tag pointing to the exact published commit; and
11
+ 3. one GitHub Release containing notes derived from the finalized `CHANGELOG.md` entry.
12
+
13
+ The npm package contains the strict allowlisted artifact tested by `npm run check:package`, including both unsigned native binaries. The project will not publish to crates.io, attach the npm tarball or native binary as a custom GitHub Release asset, add lifecycle/publication scripts, or claim signing/notarization. GitHub automatically generated source archives contain the complete tracked tree and are not substitutes for the tested npm artifact.
14
+
15
+ The exact npm version and reviewed full commit SHA are the canonical installation and audit coordinates. The GitHub Release notes must state that SHA and the npm package's registry integrity. A tag is a discovery label, not a substitute for immutable commit review, and README Git installation instructions must continue to use a full SHA.
16
+
17
+ There is no automated publication workflow. Release execution is manual; sole maintainer Revaz Zakalashvili explicitly authorized the coordinated `v0.1.0` npm publication, tag, and GitHub Release after the candidate gates.
18
+
19
+ ## Blocking gates
20
+
21
+ Every item in this section blocks the npm publication, tag, and GitHub Release. A skipped, unknown, or merely planned result is not a pass.
22
+
23
+ ### 1. Freeze and review the exact candidate
24
+
25
+ - Start from synchronized public `main` and identify one full candidate SHA.
26
+ - Ensure the candidate contains no private career content, credentials, sessions, provider output, generated local paths, or unreviewed runtime bytes.
27
+ - Review the complete diff and confirm `package.json` remains `0.1.0`, explicitly public only at `https://registry.npmjs.org/`, peer-only at runtime, and free of lifecycle/publication scripts.
28
+ - Confirm `src/`, `dist/index.js`, runtime manifest/provenance, package contents, supported targets, and the exact three native tools remain aligned.
29
+ - Do not move the candidate after its local and hosted evidence is recorded. Any content change creates a new candidate and requires the gate again.
30
+
31
+ ### 2. Human native-license review
32
+
33
+ [`native-dependency-inventory.md`](native-dependency-inventory.md) records the exact 30-package normal/build Cargo graph, selected MIT texts for all 28 crates.io packages, the two Career Core workspace packages, Rust 1.97.1 Standard Library evidence, Unicode-3.0 requirement, target dynamic imports, and the Swift/UniFFI exclusion. `npm run check:native-licenses` enforces every packaged license/notice hash, inventory coordinate, target, provenance compiler version, and file boundary. This is evidence, not legal advice, an SPDX/CycloneDX SBOM, or an automated approval.
34
+
35
+ Before publication, a human reviewer must:
36
+
37
+ - verify the inventory against Career Core commit `a3cdb4c6d7f966397e93ea4664071975bca7228c`, Cargo.lock SHA-256 `18d188cfea79128d4024dabe2e21f57e5d2098d32ffac8c4ef01243f49abb609`, and both per-target provenance records;
38
+ - confirm the documented MIT selections, exact grouped upstream texts/copyright notices, Rust Standard Library evidence, and Unicode License V3 payload satisfy the package-owned obligations for both native binaries;
39
+ - confirm the host-supplied dynamic-library boundary and that excluded Fuchsia/Swift/UniFFI dependencies are not part of either distributed target; and
40
+ - record an explicit approve/block decision without presenting the inventory as legal advice.
41
+
42
+ Independent review is preferred. When the project has only one maintainer, that sole maintainer may complete and record the review, but release notes must disclose that it was maintainer self-review rather than independent legal review. No npm publication, tag, or release may proceed while the human decision is absent or blocked. Any dependency, compiler, target, binary, provenance, or notice change invalidates the evidence and requires a fresh inventory and review.
43
+
44
+ For `v0.1.0`, sole maintainer Revaz Zakalashvili reviewed the evidence above and recorded **APPROVED** for both packaged targets. This is a maintainer release decision, not independent review or legal advice.
45
+
46
+ ### 3. Upstream artifact-expiry decision
47
+
48
+ The imported binaries and provenance remain tracked and hash-verified in this repository, but the original Career Core Actions artifacts were ephemeral:
49
+
50
+ | Artifact ID | Target | GitHub-reported expiry |
51
+ |---:|---|---|
52
+ | `8910079991` | `darwin-arm64` | `2026-08-07T21:43:37Z` |
53
+ | `8910084163` | `linux-x64-gnu` | `2026-08-07T21:43:47Z` |
54
+
55
+ Before npm publication, a human must recheck artifact availability and explicitly decide whether the tracked binaries, per-target provenance, manifest, archive identities/hashes, and public Core commit are sufficient durable provenance after expiry. If they are not sufficient, release stays blocked pending a separately approved preservation plan. The release process does not download, copy, upload, recreate, or relabel either artifact.
56
+
57
+ For `v0.1.0`, sole maintainer Revaz Zakalashvili rechecked both artifacts on 2026-08-06 and recorded **SUFFICIENT**: the tracked binaries, per-target provenance, manifest, archive identities/hashes, public Core commit, and package verification are accepted as the durable evidence after upstream expiry.
58
+
59
+ ### 4. Clean production and full audits
60
+
61
+ `npm run audit:production` must pass with zero package-owned production vulnerabilities and `npm run audit:full` must pass with zero vulnerabilities across the complete development/host-Pi tree, both at explicit `--audit-level=low`. The production audit omits development, optional, and peer trees because the tarball owns no runtime dependency tree; strict package checks separately prove there is no `node_modules` or Pi package content and that exactly four wildcard peers remain external.
62
+
63
+ Both audits invoke `process.execPath` plus the absolute npm CLI derived from the real Node installation, verify any inherited `npm_execpath`, remove omit/include/audit-level/`NODE_ENV` overrides, strictly parse bounded JSON, and reject duplicate decoded keys. `npm run check:publish` is the authoritative readiness gate but performs no publication. It is a direct Node orchestrator with no nested npm command and requires both clean audits plus extracted package/load/install proof. Pack uses the trusted absolute npm CLI; listing and extraction use verified root-owned absolute `/usr/bin/tar`, never PATH-selected tools.
64
+
65
+ The former temporary development/host-Pi acceptance was explicitly retired after upgrading the Pi development baseline to `0.84.0`; no accepted-audit file or validator remains. Do not use `npm audit fix --force`, downgrade the Pi baseline, override or patch the published Pi shrinkwrap, hand-edit lock entries, or add a replacement acceptance. A future finding blocks publication until remediated.
66
+
67
+ ### 5. Complete verification on the frozen SHA
68
+
69
+ Run with Node.js 22.19 or newer:
70
+
71
+ ```bash
72
+ npm ci
73
+ npm run build
74
+ git diff --exit-code -- dist/index.js
75
+ npm run check
76
+ npm run test:bundled-runtime
77
+ npm run audit:production
78
+ npm run audit:full
79
+ npm run check:publish
80
+ PI_OFFLINE=1 npm run test:pi-smoke
81
+ PI_OFFLINE=1 npm run test:install
82
+ CAREER_CORE_FIXTURE_ROOT=/absolute/path/to/reviewed/career-core npm run test:compat
83
+ npm ls --omit=dev --depth=0
84
+ git diff --check
85
+ ```
86
+
87
+ Requirements:
88
+
89
+ - `npm run build` may reproduce tracked `dist/index.js`; it must not alter runtime artifacts. The immediate dist diff must pass.
90
+ - All project/runtime/package/offline checks and both zero-vulnerability audits must pass, the runtime npm tree must remain empty, and `npm run check:publish` must pass.
91
+ - Compatibility must execute against an explicitly reviewed fixture checkout; a skip is not release evidence.
92
+ - No audit acceptance or not-clean full-audit claim is permitted.
93
+ - The exact final SHA must then pass both required hosted native jobs: `darwin-arm64` on macOS arm64 and `linux-x64-gnu` on Linux x64 glibc.
94
+
95
+ ### 6. Finalize notes only after all other gates pass
96
+
97
+ After every preceding gate passes, a separately committed finalization change must:
98
+
99
+ - convert the candidate notes to a dated `0.1.0` entry;
100
+ - preserve unsigned/not-notarized runtime caveats and the two supported targets;
101
+ - state that `pi-career@0.1.0` is the public npm package and that there is no crate publication or custom release asset; and
102
+ - state that both the package-owned production audit and complete development/host-Pi audit are clean at the explicit low threshold.
103
+
104
+ A commit cannot contain its own Git SHA. After the finalization commit exists, record its full SHA in the GitHub Release notes and verify npm's `gitHead` against it. Only that separately authorized final commit may receive the annotated tag, npm publication, and GitHub Release.
105
+
106
+ ## Manual release execution
107
+
108
+ After all blocking gates pass on the final clean commit and the maintainer has explicitly authorized execution:
109
+
110
+ 1. Confirm `npm whoami` identifies the intended npm account and the registry is exactly `https://registry.npmjs.org/`. Never place an npm token or one-time password in repository files, Pi messages, logs, or release notes.
111
+ 2. Reconfirm that `npm view pi-career@0.1.0 version --json` returns not found. A registry name check does not reserve the name.
112
+ 3. Create and push the unsigned annotated `v0.1.0` tag for the exact final commit.
113
+ 4. From Node 22.19.0/npm 10.9.3, publish once with lifecycle scripts disabled:
114
+
115
+ ```bash
116
+ npm publish --access public --tag latest --ignore-scripts
117
+ ```
118
+
119
+ 5. Verify `npm view pi-career@0.1.0 --json` reports the expected version, repository, four peers, tarball integrity, and `gitHead`; then perform an isolated `pi install npm:pi-career@0.1.0`, package load, bundled-runtime smoke, and removal on a supported target.
120
+ 6. Create the GitHub Release from `v0.1.0`. State the full commit SHA, npm registry integrity, supported targets, unsigned/not-notarized binaries, no crate/custom assets, zero-vulnerability package-owned production and complete development/host-Pi audits at the explicit low threshold, and that native-license evidence received sole-maintainer self-review rather than independent legal review.
121
+
122
+ Do not sign, attach assets, change repository settings, publish another registry tag/version, or retry after an ambiguous registry response without first querying the registry. npm versions are immutable; a failed post-publication check is an incident, not permission to overwrite `0.1.0`.
package/package.json ADDED
@@ -0,0 +1,91 @@
1
+ {
2
+ "name": "pi-career",
3
+ "version": "0.1.0",
4
+ "private": false,
5
+ "description": "Self-contained Pi tools, slash commands, and Agent Skill for deterministic Career Core workflows",
6
+ "license": "MIT OR Apache-2.0",
7
+ "author": {
8
+ "name": "Revaz Zakalashvili",
9
+ "url": "https://github.com/revazi"
10
+ },
11
+ "homepage": "https://github.com/revazi/pi-career#readme",
12
+ "bugs": {
13
+ "url": "https://github.com/revazi/pi-career/issues"
14
+ },
15
+ "repository": {
16
+ "type": "git",
17
+ "url": "git+https://github.com/revazi/pi-career.git"
18
+ },
19
+ "keywords": [
20
+ "pi-package"
21
+ ],
22
+ "type": "module",
23
+ "engines": {
24
+ "node": ">=22.19.0"
25
+ },
26
+ "files": [
27
+ "dist",
28
+ "docs",
29
+ "runtime",
30
+ "skills",
31
+ "CHANGELOG.md",
32
+ "SECURITY.md",
33
+ "LICENSE-APACHE",
34
+ "LICENSE-MIT",
35
+ "NOTICE"
36
+ ],
37
+ "scripts": {
38
+ "clean": "node -e \"import('node:fs/promises').then(({rm}) => rm('dist', {recursive:true, force:true}))\"",
39
+ "build": "node scripts/build.mjs",
40
+ "typecheck": "tsc --noEmit",
41
+ "test": "npm run test:process && npm run test:runtime && npm run test:workflow && npm run test:audit",
42
+ "test:process": "node --import tsx --test tests/process/process.test.mjs",
43
+ "test:runtime": "node --import tsx --test tests/runtime/runtime.test.mjs",
44
+ "test:workflow": "node --import tsx --test tests/workflow/*.test.mjs",
45
+ "test:audit": "node --test tests/audit/*.test.mjs",
46
+ "test:bundled-runtime": "node scripts/test-bundled-runtime.mjs",
47
+ "test:pi-smoke": "node scripts/test-pi-package-load.mjs",
48
+ "test:install": "node scripts/test-isolated-install.mjs",
49
+ "test:compat": "node scripts/test-bundled-runtime-compat.mjs",
50
+ "check:dist": "node scripts/check-dist.mjs",
51
+ "check:runtime-artifacts": "node scripts/check-runtime-artifacts.mjs",
52
+ "check:native-licenses": "node scripts/check-native-license-inventory.mjs",
53
+ "check:package": "node scripts/check-package.mjs",
54
+ "check:publish": "node scripts/check-publish.mjs",
55
+ "check:links": "node scripts/check-links.mjs",
56
+ "check:secrets": "node scripts/check-secrets.mjs",
57
+ "check:runtime": "node scripts/check-runtime-boundary.mjs",
58
+ "audit:production": "node scripts/audit-production.mjs",
59
+ "audit:full": "node scripts/audit-full.mjs",
60
+ "check:syntax": "node --check scripts/*.mjs scripts/lib/*.mjs tests/audit/*.mjs tests/process/*.mjs tests/runtime/*.mjs tests/workflow/*.mjs",
61
+ "check": "npm run typecheck && npm run check:dist && npm run check:runtime-artifacts && npm run check:native-licenses && npm test && npm run check:runtime && npm run check:links && npm run check:secrets && npm run check:syntax"
62
+ },
63
+ "peerDependencies": {
64
+ "@earendil-works/pi-ai": "*",
65
+ "@earendil-works/pi-coding-agent": "*",
66
+ "@earendil-works/pi-tui": "*",
67
+ "typebox": "*"
68
+ },
69
+ "devDependencies": {
70
+ "@earendil-works/pi-ai": "0.84.0",
71
+ "@earendil-works/pi-coding-agent": "0.84.0",
72
+ "@earendil-works/pi-tui": "0.84.0",
73
+ "@types/node": "24.12.4",
74
+ "esbuild": "0.28.1",
75
+ "tsx": "4.23.5",
76
+ "typebox": "1.3.7",
77
+ "typescript": "5.9.3"
78
+ },
79
+ "publishConfig": {
80
+ "access": "public",
81
+ "registry": "https://registry.npmjs.org/"
82
+ },
83
+ "pi": {
84
+ "extensions": [
85
+ "./dist/index.js"
86
+ ],
87
+ "skills": [
88
+ "./skills/career-core"
89
+ ]
90
+ }
91
+ }
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Revaz Zakalashvili
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Revaz Zakalashvili
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -0,0 +1,22 @@
1
+ # Third-party notices
2
+
3
+ `career-core` project-authored source is licensed under `MIT OR Apache-2.0`. The optional Swift binding adapter uses the following MPL-2.0 dependencies:
4
+
5
+ - UniFFI `0.30.0`
6
+ - `uniffi_bindgen` `0.30.0`
7
+ - `uniffi_core` `0.30.0`
8
+ - `uniffi_internal_macros` `0.30.0`
9
+ - `uniffi_macros` `0.30.0`
10
+ - `uniffi_meta` `0.30.0`
11
+ - `uniffi_pipeline` `0.30.0`
12
+ - `uniffi_udl` `0.30.0`
13
+
14
+ License: [Mozilla Public License 2.0](https://www.mozilla.org/MPL/2.0/)
15
+
16
+ Corresponding source: <https://github.com/mozilla/uniffi-rs/tree/v0.30.0>
17
+
18
+ UniFFI is used only by `crates/career-swift` and the pinned local binding-generation tool. Generated Swift and C declarations are produced from project-authored interface metadata by that version.
19
+
20
+ Any future distributed Swift/XCFramework artifact must include this notice, the project MIT/Apache licenses, and the source location above. No artifact is distributed or published during Phase 6.
21
+
22
+ Other Rust dependencies declare permissive license alternatives recorded in `Cargo.lock` and their crates.io package metadata. Release review must re-audit the exact locked dependency set before publication.
Binary file
@@ -0,0 +1,101 @@
1
+ {
2
+ "build": {
3
+ "cargo_version": "cargo 1.97.1 (c980f4866 2026-06-30)",
4
+ "command": [
5
+ "cargo",
6
+ "build",
7
+ "--release",
8
+ "--locked",
9
+ "-p",
10
+ "career-cli",
11
+ "--target",
12
+ "aarch64-apple-darwin"
13
+ ],
14
+ "host_arch": "arm64",
15
+ "host_os": "macos",
16
+ "locked": true,
17
+ "os_release": "Darwin 23.6.0",
18
+ "platform_key": "darwin-arm64",
19
+ "profile": "release",
20
+ "rustc_version": "rustc 1.97.1 (8bab26f4f 2026-07-14)",
21
+ "target_triple": "aarch64-apple-darwin"
22
+ },
23
+ "contract_digests": {
24
+ "capabilities": {
25
+ "schema_version": "career.capabilities.v1",
26
+ "sha256": "c45443be0ba7cfbcd4e20b28d8d100f33542e77b0b983ebf3110dddfdd71d3f3",
27
+ "size_bytes": 1855
28
+ },
29
+ "schema_catalog": {
30
+ "schema_count": 25,
31
+ "schema_version": "career.schema_catalog.v1",
32
+ "sha256": "398b093a1a6245e05a1a93eafd2162c0fe5afcb4b3ff3c7856730ac64628c5e0",
33
+ "size_bytes": 3795
34
+ },
35
+ "schema_export": {
36
+ "schema_id": "career.job_match.v1",
37
+ "sha256": "286cf0297b3f1b224f7ec7db4b06605423dbff844a38fe79d0c53fd4dea5bfde",
38
+ "size_bytes": 11526
39
+ }
40
+ },
41
+ "executable": {
42
+ "file_name": "career",
43
+ "sha256": "9e46972c1d4b2a1ca695595c0953c4198bfb12af2ba39f040e955b5b11952790",
44
+ "size_bytes": 4522688,
45
+ "version_output": "career 0.1.0"
46
+ },
47
+ "licenses_and_notices": [
48
+ {
49
+ "file_name": "LICENSE-MIT",
50
+ "sha256": "10c3e4d0fc59a6a502c18039ae76f3ff473e3f17c3428f7e417582665e65e8e9",
51
+ "size_bytes": 1075
52
+ },
53
+ {
54
+ "file_name": "LICENSE-APACHE",
55
+ "sha256": "2f2746efca80d5c78999cf97ee127ec9e3b0e86346004f71de39a7f8f8b9b1e8",
56
+ "size_bytes": 11348
57
+ },
58
+ {
59
+ "file_name": "THIRD_PARTY_NOTICES.md",
60
+ "sha256": "50c74854ed27f9347ea2f647a42a18c3c5579fd32f19a416941eab50fca59ca1",
61
+ "size_bytes": 1141
62
+ }
63
+ ],
64
+ "native_verification": [
65
+ {
66
+ "golden_fixture": "fixtures/resume/phase3/complete-analysis.expected.json",
67
+ "input_fixture": "fixtures/resume/phase3/complete-analysis.input.json",
68
+ "operation": "resume.analyze",
69
+ "output_schema_version": "career.resume_analysis.v1",
70
+ "output_sha256": "01eb6332172ea2e747be7b409fe31f646882079a36d327eb66bf3f3a92bb4acc",
71
+ "output_size_bytes": 12416
72
+ },
73
+ {
74
+ "golden_fixture": "fixtures/job/phase4b/complete-match.expected.json",
75
+ "input_fixture": "fixtures/job/phase4b/complete-match.input.json",
76
+ "operation": "job.match",
77
+ "output_schema_version": "career.job_match.v1",
78
+ "output_sha256": "872727a02f690b8269533c845e701086a90523a8579ccd0bee3abc8561764e96",
79
+ "output_size_bytes": 17598
80
+ }
81
+ ],
82
+ "package": {
83
+ "archive_file": "career-pi-runtime-darwin-arm64-aarch64-apple-darwin-a3cdb4c6d7f966397e93ea4664071975bca7228c.tar.gz",
84
+ "contents": [
85
+ "career",
86
+ "metadata.json",
87
+ "LICENSE-MIT",
88
+ "LICENSE-APACHE",
89
+ "THIRD_PARTY_NOTICES.md"
90
+ ],
91
+ "unsigned": true
92
+ },
93
+ "publication_status": "not_a_public_release",
94
+ "purpose": "maintainer_input_for_external_pi_career",
95
+ "schema_version": "career.pi_career_runtime_artifact.v1",
96
+ "source": {
97
+ "git_dirty": false,
98
+ "git_sha": "a3cdb4c6d7f966397e93ea4664071975bca7228c",
99
+ "repository": "https://github.com/revazi/career-core"
100
+ }
101
+ }
Binary file