Skip to content

README, CONTRIBUTING: 1bit-MONSTER is private now - #86

Merged
bong-water-water-bong merged 1 commit into
mainfrom
docs/1bit-monster-private
Sep 25, 2026
Merged

bong-water-water-bong merged 1 commit into
mainfrom
docs/1bit-monster-private

Conversation

@bong-water-water-bong

Copy link
Copy Markdown
Collaborator

1bit-MONSTER is now a private repository, so its links 404 for the public. This PR names it in README.md and CONTRIBUTING.md without linking to it.

Not changed: the blog posts under site/ still link to it. They are historical records.

🤖 Generated with Claude Code

…y now

Its links would 404 for the public; name it without a link.

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

context7 Bot commented Sep 25, 2026

Copy link
Copy Markdown

Docs7 for 1bit-monster/engine

Result Status Action
Deployment ➖ Not used —
Content review ➖ Did not run. This site has no agent runs available this month. Wait for the monthly reset or check your Docs7 plan. —

Commit 32a9ea4

@github-actions

Copy link
Copy Markdown

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Removed Link to Private Repository

The link to the private 1bit-MONSTER repository has been removed from CONTRIBUTING.md. While this is expected for a private repository, it's important to ensure that all references to the private repository are consistently updated across documentation to avoid confusion for contributors who may still have access or knowledge of the repository's previous public status.

This repository is a port of the working code in 1bit-MONSTER, our private development
repository, without its history.
Removed Link to Private Repository

The link to the private 1bit-MONSTER repository has been removed from README.md. This change aligns with the repository being private, but it's important to confirm that all documentation accurately reflects the current status and that no outdated references remain.

> the Laya router. The working engine is being ported from 1bit-MONSTER, our private development
> repository; see [docs/PORTING.md](docs/PORTING.md).

@bong-water-water-bong
bong-water-water-bong merged commit ee44f36 into main Sep 25, 2026
5 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the docs/1bit-monster-private branch September 25, 2026 16:43
bong-water-water-bong added a commit that referenced this pull request Sep 25, 2026
#86's unlinked 1bit-MONSTER)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bong-water-water-bong added a commit that referenced this pull request Oct 5, 2026
…-Next) (#311)

* Bump HRX: llama.cpp e57beb9721af (fork #81-#83, #86-#88)

Moves third_party/llama.cpp (1bit-MONSTER/llama.cpp 1bit/hrx-vulkan-patched)
2e5fcf56a24d -> e57beb9721af; hrx-system stays at 51b1739ae5fd.
Registry regenerated at the new pin: 290 -> 292 architectures (qwen4exp).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Bump HRX: registry at the committed pin; qwen4exp is mapped now

registry/architectures.json was generated against the previous gitlink
(registry_pins failed). tests/device_route.sh used qwen4exp as its
"not built" example; at this pin Flash-Next runs on HRX, so the test now
checks it takes the plain route and keeps zamba2 as the refused example.
Docs that listed qwen4exp as unbuilt say it is back.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant