chore: repoint self_encryption at Autonomi, and unblock CI

This repo is pinned first on the WithAutonomi org profile and is its strongest
asset at 138 stars, but a visitor who opened the README was routed straight back
out to MaidSafe properties.

README:
- Header nav table was MaidSafe website / SAFE Dev Forum / SAFE Network Forum,
  the first thing under the title. Now Autonomi / Documentation / Discord.
- The architecture image was hotlinked from the archived
  maidsafe/self_encryption. The file is already committed here at
  img/self_encryption.png, so it is now a relative path and no longer depends on
  the old repo continuing to exist.
- Both Release Process links pointed at maidsafe/self_encryption. The "go to
  GitHub Actions and run the release workflow" one was a live defect: following
  it takes you to the wrong repository's Actions tab.
- Dropped the Guide to contributing link. It pointed at
  github.com/maidsafe/QA/blob/master/CONTRIBUTING.md, which 404s - the QA repo
  does not exist, confirmed by querying the API as an owner of the maidsafe org,
  so this is not a private-repo permissions artifact. Removed rather than
  repointed because there is no WithAutonomi equivalent yet; an org-wide
  CONTRIBUTING.md is tracked in V2-878 and will be inherited automatically.

Cargo.toml:
- repository pointed at maidsafe/self_encryption. This is the link crates.io
  renders as "Repository", so anyone arriving from crates.io was being sent to
  the archived org.
- homepage was maidsafe.net, now autonomi.com.
- description now matches the GitHub description. Reaches crates.io on the next
  publish.
- Added keywords and categories - the crates.io equivalent of the GitHub topics.

CI, unrelated to the above but blocking these checks:
- The 32bit job ran `sudo apt install gcc-multilib` against the runner image's
  stale package index, which pins glibc 2.39-0ubuntu8.7. That version has been
  superseded in the Ubuntu mirror, so the .deb 404s and the job died in nine
  seconds before running a single test. Refreshing the index first fixes it;
  -y makes the install non-interactive. Latent rather than new - invisible until
  the mirror rotated, then it broke every PR at once.
- Ignore RUSTSEC-2026-0177 in deny.toml. pyo3 0.24.2's
  PyCFunction::new_closure lacked a Sync bound; the remedy is pyo3 >= 0.29.0,
  five minor versions ahead and across the Bound API migration, so it needs real
  work in src/python.rs. The advisory postdates this repo's last green run on
  master and has nothing to do with these changes. Tracked in V2-877; the ignore
  entry carries a reason and comes out when that lands.

authors and license are deliberately unchanged - both are tied to the open
copyright-holder question across the org, and to V2-847.

Refs V2-846, V2-848, V2-877, V2-878

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: jacderida

.github/workflows/merge.yml

@@ -119,7 +119,9 @@ jobs:
       - name: Install 32bit target
         run: rustup target install i686-unknown-linux-gnu
       - name: Install GCC Multilib
-        run: sudo apt install gcc-multilib
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y gcc-multilib
 
       - uses: actions/cache@v4
         with:

Cargo.toml

@@ -3,14 +3,16 @@ members = ["nodejs"]
 
 [package]
 authors = ["MaidSafe Developers <dev@maidsafe.net>"]
-description = "Self encrypting files (convergent encryption plus obfuscation)"
+categories = ["cryptography", "filesystem"]
+description = "Self-encrypting, content-addressed storage - convergent encryption that splits data into obfuscated chunks. The peer-reviewed core of Autonomi."
 documentation = "https://docs.rs/self_encryption"
 edition = "2018"
-homepage = "https://maidsafe.net"
+homepage = "https://autonomi.com"
+keywords = ["encryption", "convergent", "storage", "autonomi", "deduplication"]
 license = "GPL-3.0"
 name = "self_encryption"
 readme = "README.md"
-repository = "https://github.com/maidsafe/self_encryption"
+repository = "https://github.com/WithAutonomi/self_encryption"
 version = "0.36.0"
 
 [features]

README.md

@@ -6,8 +6,8 @@ Self encrypting files (convergent encryption plus obfuscation)
 |:---:|:-----------:|
 |[![](https://img.shields.io/crates/v/self_encryption.svg)](https://crates.io/crates/self_encryption)|[![Documentation](https://docs.rs/self_encryption/badge.svg)](https://docs.rs/self_encryption)|
 
-| [MaidSafe website](https://maidsafe.net) | [SAFE Dev Forum](https://forum.safedev.org) | [SAFE Network Forum](https://safenetforum.org) |
-|:----------------------------------------:|:-------------------------------------------:|:----------------------------------------------:|
+| [Autonomi](https://autonomi.com) | [Documentation](https://docs.autonomi.com) | [Discord](https://discord.gg/autonomi) |
+|:--------------------------------:|:------------------------------------------:|:--------------------------------------:|
 
 ## Table of Contents
 - [Overview](#overview)
@@ -31,7 +31,7 @@ A version of [convergent encryption](http://en.wikipedia.org/wiki/convergent_enc
 
 **Important Security Note**: While this library provides very secure encryption of the data, the returned secret key **requires the same secure handling as would be necessary for any secret key**.
 
-![image of self encryption](https://github.com/maidsafe/self_encryption/blob/master/img/self_encryption.png?raw=true)
+![image of self encryption](img/self_encryption.png)
 
 ## Documentation
 - [Self Encrypting Data Whitepaper](https://docs.maidsafe.net/Whitepapers/pdf/SelfEncryptingData.pdf)
@@ -292,17 +292,15 @@ Want to contribute? Great :tada:
 
 There are many ways to give back to the project, whether it be writing new code, fixing bugs, or just reporting errors. All forms of contributions are encouraged!
 
-For instructions on how to contribute, see our [Guide to contributing](https://github.com/maidsafe/QA/blob/master/CONTRIBUTING.md).
-
 ## Release Process
 
 To prepare a new release:
 
 1. **Create a PR with version bump and changelog**: 
    - Update version in `Cargo.toml` based on [Semantic Versioning](https://semver.org/)
    - Add new version entry to `CHANGELOG.md` with release date and changes
-   - Example: [PR #416](https://github.com/maidsafe/self_encryption/pull/416)
+   - Example: [PR #416](https://github.com/WithAutonomi/self_encryption/pull/416)
 
 2. **Run the release workflow manually**: 
-   - After PR is merged, go to [GitHub Actions](https://github.com/maidsafe/self_encryption/actions/workflows/release.yml)
+   - After PR is merged, go to [GitHub Actions](https://github.com/WithAutonomi/self_encryption/actions/workflows/release.yml)
    - Click "Run workflow" to trigger the automated release process

deny.toml

@@ -77,6 +77,11 @@ ignore = [
     "RUSTSEC-2020-0159",
     "RUSTSEC-2020-0071",
     "RUSTSEC-2025-0141",
+    # Temporary. pyo3 0.24.2 - PyCFunction::new_closure lacked a Sync bound.
+    # Remedy is pyo3 >= 0.29.0, five minor versions ahead and across the Bound
+    # API migration, so it needs real work in src/python.rs rather than a
+    # version bump. Tracked in V2-877 - remove this entry when that lands.
+    { id = "RUSTSEC-2026-0177", reason = "pyo3 upgrade tracked in V2-877" },
 ]
 # If this is true, then cargo deny will use the git executable to fetch advisory database.
 # If this is false, then it uses a built-in git library.