pi-career 0.1.0 → 0.2.0

package/skills/career-core/SKILL.md

@@ -1,73 +1,119 @@
 ---
 name: career-core
-description: Discovers and invokes the package-owned deterministic Career Core runtime for source-grounded resume evaluation/normalization/readiness analysis, reviewed external suggestions and replacements, assisted-variant review/materialization, job normalization, and conservative matching. Use for supported career-document analysis or local integration work.
+description: Resolves and invokes a compatible deterministic Career Core runtime for source-grounded resume evaluation/normalization/readiness analysis, reviewed external suggestions and replacements, assisted-variant review/materialization, job normalization, and conservative matching. Use for supported career-document analysis or local integration work.
 license: MIT OR Apache-2.0
-compatibility: Requires Pi with pi-career on supported darwin-arm64 or linux-x64-gnu; CAREER_CLI_PATH is an optional bounded developer/recovery override.
+compatibility: Requires Pi with pi-career and a compatible Career Core route; reviewed @revazi/career@0.1.1 targets are ARM64/x64 macOS, GNU/musl Linux, and MSVC Windows.
 metadata:
   author: revazi
-  version: "0.1.0"
+  version: "0.2.0"
 ---
 
 # Career Core through pi-career
 
-Use the package-owned Career Core runtime through the three native tools. Career Core is authoritative; the extension only transports bounded argv/stdin JSON. Never recreate scoring, schemas, errors, evidence rules, uncertainty, or repair behavior in prompts or TypeScript.
+Use `career_run` as the primary managed interface. It resolves a compatible Career Core route and discovers its exact operation catalog and self-contained schemas internally before private input, builds exact Core envelopes from ephemeral handles, captures complete bounded Core output in memory, and returns compact model-facing projections. Career Core remains authoritative for algorithms, schemas, errors, evidence, warnings, uncertainty, ordering, baselines, and assisted/non-authoritative semantics.
 
-## Privacy decision before document use
+The raw `career_core_discover`, `career_core_resume`, and `career_core_job` tools remain registered but are normally inactive. Use `/career-tools raw` only for explicit advanced schema/debugging work; `/career-tools managed` returns to the compact surface.
 
-Pi may persist tool arguments and results in session JSONL even though Career Core and this extension do not persist career documents. Before putting private resume or job content in `career_core_resume` or `career_core_job`, require the user to make an explicit Pi session-persistence decision. Recommend starting a new transient run:
+## Privacy and managed context
+
+Start every managed workflow with:
+
+```json
+{"command":"context"}
+```
+
+In a persisted Pi session, `context` returns no private handles until an explicit session-persistence decision exists. Ask the user first. If approved, call:
+
+```json
+{"command":"consent","payload":"approve"}
+```
+
+If declined, call consent with `"decline"` and recommend a new transient run:
 
 ```bash
 pi --no-session
 ```
 
-Do not claim secure erasure or removal of previous sessions, backups, shell history, provider copies, or separately saved results. If the user does not approve private content in Pi context, do not call a document tool. Local-session approval is not approval to send content to an external model/provider.
+Do not claim secure erasure or removal of previous sessions, backups, shell history, provider copies, or separately saved results. Local-session approval is not provider approval. Transient sessions require no persisted consent entry.
+
+After approval, `context` returns bounded `resume:...` handles and, when set through `/career-vacancy`, `vacancy:current`. Handles and complete Core results are process-memory-only and disappear on session/branch replacement or restart. The model sends handles instead of repeating complete source documents in later Core envelopes.
 
-## Discover first
+## `career_run` commands
 
-1. Call `career_core_discover` with `operation: "capabilities"`.
-2. Invoke only capabilities whose status is `available`; never treat planned entries as callable.
-3. Call `career_core_discover` with `operation: "schema-list"`.
-4. Export the exact input schema needed with `operation: "schema-export"` and its returned schema ID.
-5. Construct exactly one versioned input object matching that schema, serialize it as the `input_json` string, and call the relevant document tool.
+All payloads are native JSON values, never JSON strings or complete Core envelopes.
 
-Do not infer input shapes from this prose. The bundled runtime embeds the reviewed Draft 2020-12 schemas and discovery performs no network request.
+- `context`: load current original-resume/current-vacancy handles after privacy checks.
+- `consent`: payload is `"approve"` or `"decline"` in a persisted session.
+- `analyze`: `handle` is an original `resume:...` handle.
+- `match`: `handle` is an original resume; the current vacancy is implicit.
+- `suggestion-review`: `handle` is an original resume; payload is `{"suggestions":[{"basis_check_id":"...","start_line":1,"end_line":1,"source_target":"verbatim source text","source_evidence":["verbatim in-range evidence"],"suggestion":"advisory text"}]}`. Suggestions are advisory, never replacements.
+- `replacement-review`: `handle` is an original resume; payload is:
+
+```json
+{
+  "replacements": [{
+    "basis_check_id": "...",
+    "start_line": 1,
+    "end_line": 1,
+    "source_target": "verbatim source text",
+    "source_evidence": ["verbatim in-range evidence"],
+    "proposed_replacement": "..."
+  }]
+}
+```
+
+- `variant-review`: `handle` is an original resume and the current vacancy is implicit; payload is:
+
+```json
+{
+  "changes": [{
+    "section": "experience",
+    "start_line": 1,
+    "end_line": 1,
+    "original_text": "verbatim source text",
+    "proposed_text": "...",
+    "resume_evidence": ["verbatim resume evidence"],
+    "vacancy_evidence": ["verbatim vacancy evidence"]
+  }]
+}
+```
+
+- `materialize`: `handle` is the returned variant `review:...`; only after explicit user selection, payload is `{"selected_change_ids":["change-0001"]}`.
+- `detail`: `handle` is any returned result/review/variant handle; payload is `{"section":"summary|warnings|checks|evidence|changes|document|raw"}`. For one exact canonical item add `"item":"change-0001"`, `"suggestion-0001"`, or `"replacement-0001"`. Oversized model-visible detail fails rather than truncating; request a narrower section/item.
+
+Managed projections preserve all Core warnings and the relevant authority/uncertainty/discard surface. Complete authoritative JSON remains in bounded ephemeral memory for detail access and is never written to a result file.
 
 ## Deterministic slash commands
 
-On supported targets, users can run `/career-setup`, `/career-library`, `/career-vacancy`, `/career-match`, and `/career-analyze` without involving a provider/model. These commands invoke the same package-owned runtime directly rather than calling the native tools through the LLM. They scan only configured Markdown/text roots, keep assisted variants and inputs over 50,000 Unicode scalar values out of authoritative analysis/matching, require persisted-session consent before private custom entries, and never store full Core JSON.
+Users can run `/career-setup`, `/career-library`, `/career-application`, `/career-vacancy`, `/career-match`, and `/career-analyze` without involving a provider/model. `/career-vacancy`, `/career-match`, and `/career-analyze` invoke the same resolved compatible runtime directly. Local routes are preferred; exact package acquisition, when enabled, completes before private stdin opens. `/career-application` owns branch-aware company/role identity and keeps one application per Pi session; use `/new` before another company/role.
+
+`/career-workbench` remains a guided, reviewable provider handoff. It places complete selected private source in Pi's editor but never submits automatically. Prefer `career_run` rather than raw schema reconstruction after the prompt is submitted.
+
+For non-PDF variants, present canonical retained IDs and all discard codes/warnings, then stop for explicit user selection. Materialize only in a later turn with exactly those IDs and the cached exact review input. Keep the result assisted/non-authoritative and never feed it into analysis or matching. PDF input remains extracted text only: provide reviewed manual changes, do not materialize, and do not claim to preserve visual layout.
 
-Use the native tool flow below for operations not exposed by those commands or when the user explicitly requests direct schema-level work.
+A workbench `local_save_guidance` destination is suggestion-only. Never save automatically or place assisted output under `originals/`; exact path/file approval and the assisted sidecar contract remain required. Package-owned saving is still deferred.
 
-## Native tool surface
+## Advanced raw tool surface
 
-- `career_core_discover`
-  - `capabilities`
-  - `schema-list`
-  - `schema-export` (requires exact `schema_id` from the list)
-- `career_core_resume`
-  - `evaluate`
-  - `analyze`
-  - `analysis-suggestions-review`
-  - `analysis-replacements-review`
-  - `normalize`
-  - `enrich`
-  - `variant-review`
-  - `variant-materialize`
-- `career_core_job`
-  - `normalize`
-  - `match`
+- `career_core_discover`: `capabilities`, `operations`, `schema-list`, `schema-export`, `schema-bundle`
+- `career_core_resume`: `evaluate`, `analyze`, `analysis-suggestions-review`, `analysis-replacements-review`, `normalize`, `enrich`, `variant-review`, `variant-materialize`
+- `career_core_job`: `normalize`, `match`
 
-The document tools send `input_json` only to package-owned runtime stdin with `--input - --format json-compact`. They never search PATH, invoke Cargo, fetch URLs, call a provider/model, or write payload/result files. Successful tool text is the complete runtime JSON without semantic transformation.
+Raw agents remain discovery-first. Run capabilities and operations, then use exact exported/bundled schemas. Raw document tools send `input_json` only to a compatibility-validated runtime stdin with `--input - --format json-compact`; they never invoke Cargo, fetch vacancy URLs, call a provider/model, or write payload/result files. Resolver acquisition is limited to exact `@revazi/career@0.1.1`, happens before private stdin, and is disabled by `PI_OFFLINE=1`.
 
 ## Failure handling
 
 A `career.pi_error.v1` value is adapter/process status, not a deterministic career result.
 
-- `unsupported_platform` means no reviewed bundled runtime exists for this platform/libc; do not guess, download, or fall back to PATH/Cargo.
-- `bundled_runtime_invalid` means local integrity verification failed; do not request paths, hashes, environment values, or raw filesystem errors.
+- `runtime_unavailable` means no compatible local route was found and acquisition is unavailable/offline; install exact `@revazi/career@0.1.1` or configure a reviewed compatible executable.
+- `runtime_acquisition_failed` means exact-package acquisition failed; do not request npm output, paths, environment values, or raw errors.
+- `managed_contract_invalid` means an explicit selected runtime is incompatible; an invalid `CAREER_CLI_PATH` never falls back.
 - On `career_cli_error`, inspect only the nested, validated, bounded `career.error.v1`.
 - Correct typed invalid input before trying again; do not repair by guesswork or retry unchanged validation failures.
-- On `result_too_large` or `result_too_many_lines`, do not request or use partial output. Full-result export is not yet available through pi-career.
+- Raw tools may still return `result_too_large` or `result_too_many_lines`; do not request or use partial output.
+- `career_run` `managed_contract_invalid` means the selected operation catalog/schema bundles are incompatible; do not bypass discovery or fall back to raw guessed envelopes.
+- `context_required`, stale/missing handles, and session changes require a fresh `context`, not reconstructed identifiers.
+- `detail_too_large` requires a narrower section or exact item; it does not authorize truncation or result-file export.
 - Do not ask for raw stderr, paths, environment values, source copies, or hidden process errors.
 
 ## Resume operation rules
@@ -90,11 +136,11 @@ This validates an explicit, already supplied source-grounded external proposal;
 
 ### `analysis-suggestions-review`
 
-This reruns and preserves the deterministic `baseline_analysis` while reviewing at most the schema-bounded source-targeted suggestions. Retained suggestions are assisted/non-authoritative and bound to current failed canonical actions. Exact occurrence does not prove factual entailment or rewrite safety. The v1 `suggestion` is advisory text, not a replacement. Do not create selection, mutation, export, or materialization semantics.
+This reruns and preserves the deterministic `baseline_analysis` while reviewing at most the schema-bounded source-targeted suggestions. Retained suggestions are assisted/non-authoritative and bound to current failed canonical actions. Copy each `source_target` verbatim from inside the declared source lines, never use a descriptive label, prefer one complete source line, and require each `source_evidence` item to occur verbatim within the same bounds. Make one review call; report discarded items and stop instead of automatically repairing or retrying them. Exact occurrence does not prove factual entailment or rewrite safety. The v1 `suggestion` is advisory text, not a replacement. Do not create selection, mutation, export, or materialization semantics.
 
 ### `analysis-replacements-review`
 
-This reruns and preserves `baseline_analysis` and returns canonical exact before/proposed-after values for non-authoritative diff display. Preserve action/status, evidence, discard codes, and warnings. Exact occurrence does not certify factuality or rewrite safety. It creates no candidate, selection, application, export, persistence, source mutation, or materialization path.
+This reruns and preserves `baseline_analysis` and returns canonical exact before/proposed-after values for non-authoritative diff display. Copy each `source_target` verbatim from inside the declared source lines, prefer one complete source line, and keep every `source_evidence` item inside those bounds. Make one review call; report discarded items and stop instead of automatically repairing or retrying them. Preserve action/status, evidence, discard codes, and warnings. Exact occurrence does not certify factuality or rewrite safety. User answers gathered in a prior question-led turn remain user-supplied claims, not Core-certified facts. It creates no candidate, selection, application, export, persistence, source mutation, or materialization path.
 
 ### `variant-review`
 
@@ -125,10 +171,12 @@ Use original resume and original job inputs matching the exported schema. Matchi
 
 ## Output discipline
 
-- Treat returned JSON as authoritative and complete.
-- Preserve every warning, evidence item, source span, basis ID, confidence value, uncertainty status, baseline boundary, discard code, limitation, and assisted/non-authoritative label.
-- Do not reorder, truncate, silently repair, upgrade uncertainty into fact, or claim Core generated prose it only reviewed.
+- Raw Career Core tool JSON is authoritative and complete. `career_run` content is a bounded adapter projection; its `result:...`, `review:...`, or `variant:...` handle refers to the complete unchanged Core result held in ephemeral memory.
+- Use every warning, evidence item, source span, basis ID, confidence value, uncertainty status, baseline boundary, discard code, limitation, and assisted/non-authoritative label without contradiction or silent repair.
+- Do not duplicate a complete unchanged `baseline_analysis` in prose each time a review embeds it. State that the baseline was preserved; reproduce every warning, discard code, and limitation exactly; and hydrate only the scores, evidence, source spans, or canonical items needed for the request. The ephemeral complete Core result remains authoritative for the current process.
+- Keep operational narration minimal. Do not print discovered schema JSON, repeat private source text beyond bounded evidence snippets, or narrate repair attempts unless the user asks.
+- Do not reorder Core-retained items, truncate tool output, silently repair, upgrade uncertainty into fact, or claim Core generated prose it only reviewed.
 - Do not modify source documents unless the user separately requests and approves that change.
 - Never place API keys in tool input, output, files, or logs.
 
-See [`references/cli-contract.md`](references/cli-contract.md) for bundled-runtime selection and process details. Package installation and removal are in [`../../README.md`](../../README.md).
+See [`references/cli-contract.md`](references/cli-contract.md) for external runtime selection and process details. Package installation and removal are in [`../../README.md`](../../README.md).

package/skills/career-core/references/cli-contract.md

@@ -1,45 +1,67 @@
-# Bundled runtime contract reference
+# External runtime contract reference
 
-Use this reference only after reading the parent skill. Export exact schemas through `career_core_discover`; this file intentionally does not copy the authoritative schema catalog.
+Use this reference only after reading the parent skill. Career Core remains authoritative; pi-career validates its managed operation catalog and self-contained schema bundles rather than copying Core algorithms or public schemas.
 
 ## Runtime selection
 
-Normal operations use the reviewed package-owned runtime for exactly:
+Resolution order is fixed:
 
-- `darwin-arm64`
-- `linux-x64-gnu` with positive glibc detection
+1. bounded absolute `CAREER_CLI_PATH`;
+2. `career` on PATH;
+3. package-local exact `@revazi/career@0.1.1`;
+4. acquisition of exact `@revazi/career@0.1.1` from the canonical npm registry;
+5. stable installation guidance.
 
-Selection order is a bounded absolute `CAREER_CLI_PATH` developer/recovery override first, then the verified bundled target. There is no PATH, sibling-checkout, Cargo, install-script, or download fallback. Windows, macOS x64, Linux arm64/musl, and unknown targets fail closed with `unsupported_platform`.
+There is no sibling-checkout, Cargo, source-build, lifecycle-script, arbitrary download, PATH-selected npm/npx, or unpinned package fallback. `PI_OFFLINE=1` disables acquisition. A route is cached only in memory and invalidated when `CAREER_CLI_PATH` or PATH changes. npm acquisition may leave ordinary cache/`_npx` data and does not provide secure erasure.
 
-Before first bundled execution per process, pi-career verifies the regular file's exact mode, size, and SHA-256 against its committed runtime manifest. A mismatch fails as `bundled_runtime_invalid`. These errors are payload-free and must not be expanded with platform details, paths, hashes, environment values, or raw failures.
+Every caller-controlled route must pass the exact Core 0.1.1 operation catalog and required self-contained schema bundles before private stdin opens. An invalid explicit override never falls back. Compatibility probes contain no private document input. If a cached automatic executable later fails before its operation emits `spawn`, pi-career may advance once; cancellation, timeout, and any started operation never retry another route.
 
-## Discovery and operations
+Package-local/acquired routes invoke the reviewed package launcher directly with the real Node executable. The launcher owns native target/libc, package/provenance mapping, Unix mode or Windows file invariant, size, format, architecture, and SHA-256 verification. Its reviewed targets are `darwin-arm64`, `darwin-x64`, `linux-x64-gnu`, `linux-arm64-gnu`, `linux-x64-musl`, `linux-arm64-musl`, `win32-x64-msvc`, and `win32-arm64-msvc`.
 
-Use only the three native tools:
+## Managed discovery
 
-- `career_core_discover`: `capabilities`, `schema-list`, `schema-export`
-- `career_core_resume`: `evaluate`, `analyze`, `analysis-suggestions-review`, `analysis-replacements-review`, `normalize`, `enrich`, `variant-review`, `variant-materialize`
-- `career_core_job`: `normalize`, `match`
+`career_run` internally invokes and caches only non-sensitive metadata from:
+
+- `career operations --format json-compact`
+- `career schema bundle --id <required-input-schema> --format json-compact`
+
+The adapter requires exact `career.operation_catalog.v1` capability mappings, CLI paths, transports, input/output schemas, byte ceilings, and all-local bundle references. Incompatibility fails closed. These bootstrap results are not exposed to the model during the normal managed flow.
+
+Every successful machine JSON result is completely serialized by Core before stdout and bounded to 33,554,432 bytes including framing. Managed execution captures the complete result in bounded ephemeral memory, removes only one framing newline, and projects model-visible results no larger than 50,000 bytes. It never truncates Core output or writes a result file.
 
-Invoke only capabilities whose status is `available`. Pass one exact versioned JSON object in `input_json`; the adapter writes it only to runtime stdin. Do not concatenate document text into commands, place source content in argv, or infer schemas from prose.
+## Tool surfaces
 
-## Machine framing
+The normal active surface is:
+
+- `career_run`: context, consent, analyze, match, suggestion-review, replacement-review, variant-review, materialize, and detail through ephemeral handles
+
+The following raw tools stay registered but are normally inactive:
+
+- `career_core_discover`: `capabilities`, `operations`, `schema-list`, `schema-export`, `schema-bundle`
+- `career_core_resume`: `evaluate`, `analyze`, `analysis-suggestions-review`, `analysis-replacements-review`, `normalize`, `enrich`, `variant-review`, `variant-materialize`
+- `career_core_job`: `normalize`, `match`
 
-- The adapter uses `--format json-compact`; successful runtime output is one JSON document with one framing newline.
-- Known diagnostics are one bounded `career.error.v1` on stderr with a nonzero status.
-- The runtime makes no implicit network request and does not modify input.
-- Single-document input is bounded at 262,144 UTF-8 bytes; composite job-match and variant envelopes are bounded at 1,048,576 bytes.
+`/career-tools raw` explicitly activates the raw tools; `/career-tools managed` removes them from active model context. Raw agents remain discovery-first and pass one exact versioned JSON object in `input_json`.
 
-## Pi adapter framing
+## Process and machine framing
 
-The native tools use direct `spawn(executable, argv, { shell: false })`, stdin-only document JSON, fixed operation mappings, timeout/cancellation cleanup, separate stdout/stderr capture bounds, fatal UTF-8 decoding, and exact-one-object success.
+- Direct `spawn(command, fixedArgv, { shell: false })` only.
+- Package launchers are fixed argument prefixes invoked by the real Node executable.
+- Document content appears only in stdin with `--input -`, never argv, and stdin opens only after `spawn`.
+- Machine output uses `--format json-compact`.
+- Successful Core output is exactly one JSON object with one framing newline and no stderr.
+- Known diagnostics are one bounded `career.error.v1` on stderr with nonzero status.
+- Single-document input is bounded at 262,144 bytes; match and variant composites at 1,048,576 bytes.
+- Timeout/cancellation owns child termination and cleanup.
+- Fatal UTF-8, multiple JSON documents, unexpected successful stderr, or capture overflow fail closed.
+- No payload/result temp file, model/provider call, vacancy URL fetch, telemetry, post-launch retry, or repair exists at this boundary.
 
-Successful JSON is returned complete, with only the single framing newline removed. The process adapter writes no payload/result files and has no model/provider/network behavior. The separate deterministic slash-command layer calls this process helper directly and owns only its bounded config, scan, UI, and custom-session-entry behavior.
+The sole network-capable behavior is bounded acquisition of exact `@revazi/career@0.1.1` after local routes fail. It derives npm from real Node, rejects conflicting `npm_execpath`, has fixed time/output bounds and process-tree cancellation, receives no private input, and finishes before document stdin opens.
 
-Known adapter failures use `career.pi_error.v1`. Only `career_cli_error` may include a nested strictly validated allowlisted `career.error.v1`. Other errors do not expose raw diagnostics, input/output, executable paths, hashes, platform details, environment values, or Node/filesystem errors.
+Raw tools retain the 50,000-byte/2,000-line model-context ceiling and fail without partial output. Managed operations use Core's 32-MiB capture ceiling internally and expose compact/hydratable results.
 
-If a complete result exceeds 50,000 bytes or 2,000 lines, the tool fails as `result_too_large` or `result_too_many_lines`. Do not request or use partial output. Full-result export is not yet available through pi-career.
+## Ephemeral handles and privacy
 
-## Privacy
+Resume handles resolve current scanned originals on demand rather than retaining every resume body. Review handles retain the exact private review input required for deterministic materialization; result/review/variant handles retain complete Core JSON. The registry is count/byte bounded, process-memory-only, and cleared on session/branch replacement and shutdown. Evicted or stale handles fail closed.
 
-Pi may persist native tool arguments/results in session JSONL. Require an explicit decision before private use and recommend a new `pi --no-session` run when session persistence is not wanted. This is not secure erasure and is separate from consent for any external provider.
+Persisted Pi sessions require an explicit consent entry before private handles are returned. Transient `pi --no-session` runs do not write those entries. This is not secure erasure and is separate from provider consent. Tool calls and compact results may still become part of normal Pi/provider context after submission.

package/runtime/LICENSE-APACHE

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright 2026 Revaz Zakalashvili
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/runtime/THIRD_PARTY_NOTICES.md

@@ -1,22 +0,0 @@
-# Third-party notices
-
-`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:
-
-- UniFFI `0.30.0`
-- `uniffi_bindgen` `0.30.0`
-- `uniffi_core` `0.30.0`
-- `uniffi_internal_macros` `0.30.0`
-- `uniffi_macros` `0.30.0`
-- `uniffi_meta` `0.30.0`
-- `uniffi_pipeline` `0.30.0`
-- `uniffi_udl` `0.30.0`
-
-License: [Mozilla Public License 2.0](https://www.mozilla.org/MPL/2.0/)
-
-Corresponding source: <https://github.com/mozilla/uniffi-rs/tree/v0.30.0>
-
-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.
-
-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.
-
-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.

package/runtime/darwin-arm64/provenance.json

@@ -1,101 +0,0 @@
-{
-  "build": {
-    "cargo_version": "cargo 1.97.1 (c980f4866 2026-06-30)",
-    "command": [
-      "cargo",
-      "build",
-      "--release",
-      "--locked",
-      "-p",
-      "career-cli",
-      "--target",
-      "aarch64-apple-darwin"
-    ],
-    "host_arch": "arm64",
-    "host_os": "macos",
-    "locked": true,
-    "os_release": "Darwin 23.6.0",
-    "platform_key": "darwin-arm64",
-    "profile": "release",
-    "rustc_version": "rustc 1.97.1 (8bab26f4f 2026-07-14)",
-    "target_triple": "aarch64-apple-darwin"
-  },
-  "contract_digests": {
-    "capabilities": {
-      "schema_version": "career.capabilities.v1",
-      "sha256": "c45443be0ba7cfbcd4e20b28d8d100f33542e77b0b983ebf3110dddfdd71d3f3",
-      "size_bytes": 1855
-    },
-    "schema_catalog": {
-      "schema_count": 25,
-      "schema_version": "career.schema_catalog.v1",
-      "sha256": "398b093a1a6245e05a1a93eafd2162c0fe5afcb4b3ff3c7856730ac64628c5e0",
-      "size_bytes": 3795
-    },
-    "schema_export": {
-      "schema_id": "career.job_match.v1",
-      "sha256": "286cf0297b3f1b224f7ec7db4b06605423dbff844a38fe79d0c53fd4dea5bfde",
-      "size_bytes": 11526
-    }
-  },
-  "executable": {
-    "file_name": "career",
-    "sha256": "9e46972c1d4b2a1ca695595c0953c4198bfb12af2ba39f040e955b5b11952790",
-    "size_bytes": 4522688,
-    "version_output": "career 0.1.0"
-  },
-  "licenses_and_notices": [
-    {
-      "file_name": "LICENSE-MIT",
-      "sha256": "10c3e4d0fc59a6a502c18039ae76f3ff473e3f17c3428f7e417582665e65e8e9",
-      "size_bytes": 1075
-    },
-    {
-      "file_name": "LICENSE-APACHE",
-      "sha256": "2f2746efca80d5c78999cf97ee127ec9e3b0e86346004f71de39a7f8f8b9b1e8",
-      "size_bytes": 11348
-    },
-    {
-      "file_name": "THIRD_PARTY_NOTICES.md",
-      "sha256": "50c74854ed27f9347ea2f647a42a18c3c5579fd32f19a416941eab50fca59ca1",
-      "size_bytes": 1141
-    }
-  ],
-  "native_verification": [
-    {
-      "golden_fixture": "fixtures/resume/phase3/complete-analysis.expected.json",
-      "input_fixture": "fixtures/resume/phase3/complete-analysis.input.json",
-      "operation": "resume.analyze",
-      "output_schema_version": "career.resume_analysis.v1",
-      "output_sha256": "01eb6332172ea2e747be7b409fe31f646882079a36d327eb66bf3f3a92bb4acc",
-      "output_size_bytes": 12416
-    },
-    {
-      "golden_fixture": "fixtures/job/phase4b/complete-match.expected.json",
-      "input_fixture": "fixtures/job/phase4b/complete-match.input.json",
-      "operation": "job.match",
-      "output_schema_version": "career.job_match.v1",
-      "output_sha256": "872727a02f690b8269533c845e701086a90523a8579ccd0bee3abc8561764e96",
-      "output_size_bytes": 17598
-    }
-  ],
-  "package": {
-    "archive_file": "career-pi-runtime-darwin-arm64-aarch64-apple-darwin-a3cdb4c6d7f966397e93ea4664071975bca7228c.tar.gz",
-    "contents": [
-      "career",
-      "metadata.json",
-      "LICENSE-MIT",
-      "LICENSE-APACHE",
-      "THIRD_PARTY_NOTICES.md"
-    ],
-    "unsigned": true
-  },
-  "publication_status": "not_a_public_release",
-  "purpose": "maintainer_input_for_external_pi_career",
-  "schema_version": "career.pi_career_runtime_artifact.v1",
-  "source": {
-    "git_dirty": false,
-    "git_sha": "a3cdb4c6d7f966397e93ea4664071975bca7228c",
-    "repository": "https://github.com/revazi/career-core"
-  }
-}